Skip to main content
Read only Returns what actually HAPPENED on one call: its transcript, the post-call summary, notes, the recording link, and post-call-analysis field order. This is the only way to read a SINGLE call’s transcript — get_call returns metadata (status, duration, cost) but never the conversation. Use it for “what did the agent say on that call?”, “why did this one go wrong?”, or to quote a caller’s own words. Transcripts can be long; ask only for the fields you need. The recording link is returned only with include_recording: true, which you set only when the user explicitly asks for the audio.

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: call_id.

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.