Dialpad MCP server

dialpad_list_calls

Read-onlyIdempotent

Lists finished calls newest first with start-time and target filters (user, office, department, call center), plus cursor pagination for additional pages.

Instructions

List finished calls, newest first: times, direction, duration, internal and external number, contact and target. Filter by start time range and by target (user, office, department, call center...). Returns one page; use next_cursor for more. Contains personal information - admin-gated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dialpad_list_calls"
  }
}

Input Schema

Name	Required	Description
`full`	No	Return every field of each item instead of the main fields only. Larger output; use only when needed.
`cursor`	No	Cursor from next_cursor of the previous page, to get the next page.
`target_id`	No	Only calls for this target ID. Needs target_type.
`target_type`	No	Type of target_id.
`started_after`	No	Only calls that started after this time (ISO 8601, e.g. 2026-11-01T00:00:00+11:00, or epoch milliseconds).
`started_before`	No	Only calls that started before this time (ISO 8601 or epoch milliseconds).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description still adds real value: newest-first ordering, single-page semantics with next_cursor, and an admin-gated / contains-PII warning. It stops short of page-size limits or rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence plus three short follow-ons; scope, return fields, filtering, pagination, and the gating warning are all present with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six optional parameters and no output schema, the description carries the return-value burden and does so by naming the fields returned, plus pagination and access constraints. Minor gaps remain around default page size and timezone handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in the schema. The description echoes the time-range and target filters and clarifies that target can be a user, office, department, or call center, but adds no syntax or format detail beyond what the schema states (ISO 8601 / epoch ms, enum values).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List finished calls, newest first" gives a specific verb, a resource, and a meaningful qualifier (finished, i.e. not in-progress), then enumerates the returned fields. It is distinguishable from the get_* siblings by being a bulk list, though it never names an alternative tool explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'finished calls' scoping and target/time-range filtering imply when to reach for this tool, and 'use next_cursor for more' tells the agent how to continue. However, there is no explicit statement of when to use dialpad_get_call for a single call, or of any prerequisites beyond 'admin-gated'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.