Dialpad MCP server

dialpad_list_call_subscriptions

Read-onlyIdempotent

List call event subscriptions to see which call states are sent to which webhook and whether each is enabled, with optional target filtering and pagination.

Instructions

List call event subscriptions (which call states are sent to which webhook, and whether each is enabled). Used by the N8N call-to-ticket workflow.

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_call_subscriptions"
  }
}

Input Schema

Name	Required	Description
`cursor`	No	Cursor from next_cursor of the previous page, to get the next page.
`target_id`	No	Only subscriptions for this target. Needs target_type.
`target_type`	No	Type of target_id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so safety is covered. The description adds useful domain semantics (subscriptions map call states to webhooks and carry an enabled flag), but says nothing about permissions, pagination behavior, or result size, which limits it to moderate added value.

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?

Two sentences, front-loaded with the core action and parenthetically explaining the resource. The workflow note is arguably extraneous but short and contextually useful; nothing is padded.

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?

For a read-only list tool with full schema coverage and rich annotations, the description covers what the tool returns conceptually (call states, webhook targets, enabled status) even though no output schema exists. Pagination semantics are left to the schema's cursor description, which is acceptable.

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 cursor, target_id, and target_type are already fully documented with an enum for target_type. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb and resource ('List call event subscriptions') and clarifies what a subscription is via the parenthetical about call states, webhooks, and enabled flags. It does not name the sibling 'dialpad_get_call_subscription' or 'dialpad_list_webhooks' to sharpen the distinction, but the list-vs-get split is clear enough.

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 note that it is 'Used by the N8N call-to-ticket workflow' implies a usage context, but there is no explicit when-to-use or when-not-to-use guidance relative to get_call_subscription, update_call_subscription, or list_webhooks. The agent must infer selection from the verb alone.

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