Skip to main content
Read only Parses a small CSV/Excel leads file WITHOUT creating anything — same preview/validation the dashboard’s batch call upload wizard runs before letting a batch start. Returns how many rows are valid vs. invalid, and for each invalid row, which phone number failed and why (bad country code, invalid length, destination not allowed by this org’s calling rules, etc.). Use this on the file before create_batch_call: if invalid_row_count > 0, show the user the specific bad rows, get them fixed or dropped, then call create_batch_call with the corrected file. Same file_base64 size limit as create_batch_call (a few dozen rows).

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: agent_id, agent_version_number.
  • 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.

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

Confirm the response is not marked isError, parse content[0].text as JSON, and verify that returned IDs and workspace data match the request.

Retry safety

This tool does not change workspace data. Retrying after a transient transport failure is safe.