Skip to main content
Read only Returns the leads (contacts) the user uploaded to one of their own batch call campaigns, given its batch_id. For each lead: its id (prefixed lead_), the phone number, the notes and the dynamic variables from the uploaded leads file. Nothing else about the lead is returned, and only batches of the authenticated workspace can be read. Use list_batch_calls to find the batch_id.

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: batch_id.
  • If your OAuth grant covers several workspaces, also pass organization_id with the workspace to act in, from List My Organizations.

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.