Skip to main content
Billable - retry unsafe Creates a batch call campaign from a small lead list and starts dialing real phone numbers immediately. This is NOT a read-only action, spends real money, and cannot be undone once calls go out (the campaign itself can be cancelled afterward with update_batch_call_status, but any calls already placed are not). Requires confirm: true — only set this after the user has explicitly approved starting this specific batch, never preemptively. Only suitable for short lists (a few dozen leads at most) — for larger campaigns, tell the user to use the dashboard upload instead. Recommended order: clean_batch_call_names on the name column, then preview_batch_call_leads on the file, resolve any issues with the user, THEN call this. Leads file, in this order of preference: the file argument when the user attached a file in the chat (pass the attachment, never re-encode it); otherwise an upload_id from create_upload_url for any real file; file_text only for a few rows the user typed into the conversation. If the user has not given any leads yet, ask for them and say they can either paste the numbers or attach their CSV/Excel file. Either way the file needs a phone_number column (and optionally name/other columns as dynamic variables). agent_version_number must be a PUBLISHED version — the org’s phone number is bound to a specific agent+version pair, not just the agent, and that binding only exists once the version is published. Use get_agent or list_agent_versions first to find the right version_number.

Parameters

Complete input schema

Registered output schema

Before you call

  • Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
  • Provide the required parameters: title, agent_id, agent_version_number, confirm.
  • Provide one file source: a host attachment, a completed upload_id, or supported inline content. The optional file fields are alternatives; omitting all of them does not submit a file. See MCP file uploads.
  • Set confirm: true only after the user approves the exact target and action.

Example MCP request

Send tools/call after your client completes MCP initialization. Replace placeholder values with IDs and inputs from your workspace. For object and array parameters, follow the nested requirements in the parameter description instead of treating an empty value as complete.
Successful results include structuredContent and a text content block containing the same JSON. Check isError first, then read structuredContent or parse content[0].text. See MCP responses and errors for the full envelope and failure behavior.

Verify the result

Store the returned resource ID and confirm the response is not marked isError. Call Get Agent to read the affected resource. Verify the call, batch, or purchase state before retrying.

Retry safety

This tool can spend wallet balance or start real calls. After a timeout, inspect the relevant resource before retrying so you do not duplicate the action.