get_call_stats
readsOne of the tools an AI assistant can call on an Avrosh account.
What it does
How much the assistant handled over a window of days: calls taken and answered, average length, conversations across every channel, how many ended up with a human, and what came out of them - bookings, orders, jobs. Also a per-day series with zeros for quiet days, so a chart drawn from it does not invent a busier business than the one that exists. Every number is counted from rows the business already has; nothing here is an estimate.
This is the exact text the model reads before deciding to call.
Parameters
business_idstringrequired
The id returned by list_businesses.
daysnumberoptional
Whole days back from now, 1-365. Default 30.
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": "get_call_stats",
"arguments": {
"business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
"days": 7
}
}
}'