> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Call Details

> Use the get_call_details MCP tool on the DialNexa remote MCP server.

<span data-api-safety-label="read-only"><Badge color="gray" size="sm" shape="pill">Read only</Badge></span>

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.

## Parameters

| Name      | Type     | Required | Description                                                                                                                      |
| --------- | -------- | -------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `call_id` | `string` | Yes      | The call ID, e.g. call\_abc123 — from list\_calls or get\_call                                                                   |
| `fields`  | `array`  | No       | Which parts to return. Defaults to transcript + summary + notes. Ask for recording\_url only when the user wants the audio link. |

## 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.

```json theme={null}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_call_details",
    "arguments": {
      "call_id": "VALUE"
    }
  }
}
```

The server returns one text content block. Parse `content[0].text` as JSON when the tool succeeds. See [MCP responses and errors](/docs/mcp-tools/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.

## Related MCP tools

* [List Calls](/docs/mcp-tools/calls/list-calls): `list_calls`
* [Get Call](/docs/mcp-tools/calls/get-call): `get_call`

## Related guides

* [Connect to the DialNexa MCP server](/docs/mcp-tools/overview)
* [Calls MCP tools](/docs/mcp-tools/calls/overview)
* [MCP responses and errors](/docs/mcp-tools/errors)