DevelopersChanges data

create_call_list

API reference — one of the tools an AI assistant can call on an Avrosh account.

What it does

Start a new outbound campaign. It is created as a DRAFT and cannot dial anybody: a human still has to attest, in the dashboard, that the people on it may lawfully be called, and no assistant can do that step. Say so when you report back rather than implying the campaign is live. `calling_window` is weekly and in the business's own timezone, and LEAVING IT OUT MEANS NEVER - an empty window is not 'any time', it is a campaign that will not place a call.

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

Parameters

business_idstringrequired

The id returned by list_businesses.

namestringrequired

What the operator will recognise it by.

objectivestringoptional

What the call is for, in one line.

voicemail_modestringoptional

Default 'hangup'. 'leave_message' requires voicemail_script.

one of: hangup · leave_message

voicemail_scriptstringoptional

What to say to a machine. Required for leave_message.

max_attemptsnumberoptional

How many tries per number, 1-10. Default 3.

Request

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":"create_call_list","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","name":"March follow-ups","objective":"ask whether they want to rebook"}}}'

Response

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

{
  "id": "cl_2…",
  "status": "draft",
  "consentAttestedAt": null
}

Connecting

Paste the URL into your assistant and log in. Avrosh implements OAuth 2.1, so an MCP client discovers the authorisation server, registers itself, and opens a browser asking you to sign in here. That is the whole setup: nothing to copy, no key to keep, and nothing to rotate later.

https://us.avrosh.com/mcp

For something with no browser to log in with — a cron job, a script, an automation platform — there is a second door: a bearer key made in the dashboard under Docs, shown once because only its hash is stored, and revocable at any time.

curl https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY"

Either way the boundary is the same one: an assistant reaches every business on the account it signed in to, and no others. There are no scopes to configure and nothing to switch on — what bounds it is whose account it is, enforced in the database rather than by a permission anybody sets.