set_callback_window

writes

One of the tools an AI assistant can call on an Avrosh account.

What it does

When this business is willing to ring somebody back, weekly and in its OWN timezone. ⚠️ REPLACES the whole schedule - send every day that should be open, not just the one being changed, or the others are dropped. An EMPTY window turns callbacks off entirely: the AI will stop offering to call anybody back, which is the correct way to switch the feature off and is not a mistake. Confirm the days with the operator before sending, because a day left out is a day the phone does not ring back.

This is the exact text the model reads before deciding to call.

Parameters

business_idstringrequired

The id returned by list_businesses.

windowobjectrequired

Weekday keys with open/close in 24h business-local time, e.g. {"mon":{"open":"09:00","close":"17:00"},"tue":{"open":"09:00","close":"17:00"}}. {} means no callbacks.

max_attemptsnumberoptional

How many times to try one callback, 1-3.

Response

The result arrives as an MCP content block; the JSON in the panel is what the text field parses to.

Connecting

Point any MCP client at https://us.avrosh.com/mcp and log in — OAuth 2.1, no key to paste.

The panel here uses the other door: a bearer key made in the dashboard, for a script or a cron job with no browser to sign in with. Both reach the same endpoint. Full notes on the reference overview.

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "set_callback_window",
      "arguments": {
        "business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
        "window": {
          "mon": {
            "open": "09:00",
            "close": "17:00"
          },
          "tue": {
            "open": "09:00",
            "close": "17:00"
          }
        },
        "max_attempts": 2
      }
    }
  }'