Dialpad MCP server

dialpad_list_contacts

Read-onlyIdempotent

Lists company-shared Dialpad contacts, optionally including local contacts, with name filtering and pagination; returns names, companies, phones, and emails.

Instructions

List company-shared Dialpad contacts (and local contacts with include_local), with name, company, phones and emails. Filter by name. 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_contacts"
  }
}

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.
`name`	No	Text to match in the contact name.
`cursor`	No	Cursor from next_cursor of the previous page, to get the next page.
`owner_id`	No	Only this user's local contacts.
`include_local`	No	Also include users' local (personal) contacts.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds value beyond them by disclosing pagination semantics ('returns one page'), the PII nature of the data, and the admin-gating requirement. It does not describe rate limits or ordering, keeping it short of a 5.

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

Conciseness4/5

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

Four short sentences, front-loaded with purpose and followed by fields, filtering, pagination and the access caveat. Every sentence carries information, though 'Filter by name' partly restates the schema's name parameter and could be trimmed.

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 no output schema, the description compensates by enumerating the returned fields and explaining the paging model. Access requirements and PII sensitivity are noted. For a five-parameter, fully documented list tool this is close to complete, missing only ordering or result-size expectations.

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%, so all five parameters are already documented in the input schema, establishing a baseline of 3. The description reinforces the meaning of include_local and the name filter but adds no syntax, matching rules, or format detail beyond the schema; the 'next_cursor' reference also differs in name from the actual 'cursor' parameter.

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?

The description opens with a specific verb and resource ('List company-shared Dialpad contacts') and immediately scopes it against the local-contact variant, listing the returned fields (name, company, phones, emails). An agent can distinguish this from dialpad_get_contact or dialpad_create_contact without opening any schema.

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?

It gives concrete when-to-use signals: set include_local to also pull personal contacts, filter by name, and use next_cursor for further pages. It also notes the admin-gating prerequisite. It stops short of naming an alternative tool for single-contact lookups, so it never explicitly says when not to use this.

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