cancel_callback
writesOne of the tools an AI assistant can call on an Avrosh account.
What it does
Call off a promised callback, with a reason. The row is kept rather than deleted, because "we said we would ring and then did not" is something the business may have to explain later, and a row that vanished explains nothing. The reason is required for the same purpose.
This is the exact text the model reads before deciding to call.
Parameters
business_idstringrequired
The id returned by list_businesses.
callback_idstringrequired
From list_callbacks.
reasonstringrequired
Why it is being called off. Kept on the record.
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": "cancel_callback",
"arguments": {
"business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
"callback_id": "cb_1…",
"reason": "customer came in person"
}
}
}'