start_call_list

writes

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

What it does

Start dialling a campaign. Refused unless it has been attested and has a calling window, and that refusal comes from the database rather than from this tool. `calling_window` is the hours the dialler is allowed to place calls in the business's own timezone, as day keys mon..sun each {open:'09:00', close:'17:00'}; a day left out is a day nobody is called. Set one that a person would find reasonable to receive: the window is what keeps a campaign the right side of local calling-hours rules, and it is not optional. Stop a running campaign with update_call_list status 'paused'.

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

Parameters

business_idstringrequired

The id returned by list_businesses.

list_idstringrequired

From list_call_lists.

calling_windowobjectoptional

Optional if the campaign already has one. Day keys mon..sun, each {open:'HH:MM', close:'HH:MM'}, in the business's timezone. Omitted days are never called.

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": "start_call_list",
      "arguments": {
        "business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
        "list_id": "7c2e...",
        "calling_window": {
          "mon": {
            "open": "09:00",
            "close": "17:00"
          }
        }
      }
    }
  }'