import_call_targets
writesOne of the tools an AI assistant can call on an Avrosh account.
What it does
Add numbers to a DRAFT or paused campaign. Numbers are normalised HERE against `dial_code`, so pass them as they came from the customer's own records rather than reformatting them yourself - and pass the dial code of the country those records belong to, never a guess. Anything already on the do-not-call list is silently left out and returned in `suppressed`: that is correct, do not retry it and do not tell the operator it failed. Rows that could not be read at all come back in `rejected` with a reason. Adding numbers still does not make the campaign runnable - only a human attesting to consent does that.
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.
dial_codestringrequired
e.g. '+62'. Used for local-format numbers.
rowsarrayrequired
Up to 1000 per call. Page larger files.
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": "import_call_targets",
"arguments": {
"business_id": "926135ac-487d-4367-8bad-25397d0d4b87",
"list_id": "cl_2…",
"dial_code": "+62",
"rows": [
{
"phone": "0812-3456-7890",
"name": "Sari",
"external_id": "crm-4471"
}
]
}
}
}'