Dialpad MCP server

dialpad_get_stats_export

Read-onlyIdempotent

Check a stats export by request ID for processing, complete, or failed status and a CSV download URL when complete. Admin-only because results can include personal data.

Instructions

Check a stats export started with dialpad_create_stats_export: status (processing, complete, failed) and, when complete, a download URL for the CSV. Contains personal information - admin-gated.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	request_id returned by dialpad_create_stats_export.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses the returned state machine (processing, complete, failed), that the URL only exists when complete, that results contain personal information, and that access is admin-gated. The admin-gating and PII disclosure are exactly the kind of behavioral context annotations cannot express.

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?

Two compact sentences, front-loaded with the action and its origin tool, then the outcome values and sensitivity flag. No redundant or filler wording.

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

Completeness5/5

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

Although there is no output schema, the description explains what is returned (status and, conditionally, a CSV download URL), which is the critical return information. With a single fully documented parameter and full annotation coverage, nothing needed for correct invocation is missing.

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 coverage is 100% and the schema description already explains that id is the request_id returned by dialpad_create_stats_export, so the description adds no meaning beyond the structured field. A baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource ("Check a stats export") and immediately scopes it to exports created by dialpad_create_stats_export, which distinguishes it from the create sibling by name. It also names the two things it returns: status and a download URL.

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

Usage Guidelines4/5

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

The phrase "started with dialpad_create_stats_export" establishes the prerequisite and the intended polling workflow, which is the key usage context. It stops short of explicit exclusions or guidance on polling cadence/retry, so it does not reach the 5 bar.

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