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

# List Calls

> Use the list_calls 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 call logs for the organization, filterable by agent, status, sentiment, and date range. Use this when the user asks about call history or outcomes across multiple calls. For a single known call, use get\_call instead.

## Parameters

| Name         | Type     | Required | Description                                                                                                                       |
| ------------ | -------- | -------- | --------------------------------------------------------------------------------------------------------------------------------- |
| `agent_id`   | `string` | No       | Filter by agent ID, e.g. agent\_abc123. Comma-separate multiple IDs.                                                              |
| `status`     | `string` | No       | Filter by call status. One of: initiated, received, sent, did\_not\_pick, busy, failed, no\_answer, completed, created, cancelled |
| `sentiment`  | `string` | No       | Filter by detected sentiment. One of: positive, neutral, negative, unknown                                                        |
| `start_date` | `string` | No       | ISO 8601 date — only calls on/after this date                                                                                     |
| `end_date`   | `string` | No       | ISO 8601 date — only calls on/before this date                                                                                    |
| `end_reason` | `string` | No       | Filter by hang-up reason                                                                                                          |
| `page`       | `string` | No       | Page number, default 1                                                                                                            |
| `limit`      | `string` | No       | Results per page, default 10, max 50                                                                                              |

## Before you call

* Connect and initialize the MCP client with OAuth or an API key for the intended workspace.
* This tool has no required arguments.

## 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": "list_calls",
    "arguments": {}
  }
}
```

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

* [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)