DevelopersRead only

get_call_stats

API reference — one 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.

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":"get_call_stats","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","days":7}}}'

Response

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

{
  "days": 7,
  "calls": {
    "total": 34,
    "answered": 31,
    "avgDurationSeconds": 96
  },
  "conversations": 58,
  "escalations": 4,
  "outcomes": {
    "bookings": 9,
    "orders": 3,
    "requests": 6
  }
}

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.