Dialpad MCP server

dialpad_update_call_subscription

Pause, resume, or change the call states sent by a Dialpad call event subscription. Use it to toggle event delivery on or off without changing the destination URL; admin approval required.

Instructions

Turn a call event subscription on or off, or change which call states it sends (the N8N call-to-ticket workflow pauses and resumes its subscription this way). Does not change where events are sent. Proposal: an administrator must approve it before it runs.

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

Input Schema

Name	Required	Description
`id`	Yes	Subscription ID (from dialpad_list_call_subscriptions).
`enabled`	No	true to send events, false to pause.
`call_states`	No	Call states to send, e.g. ["connected"] or ["hangup","recording"]. Replaces the current list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (openWorldHint=true, destructiveHint=false), and the description adds information annotations cannot carry: the change is gated by an administrator approval step before execution. It also discloses that call_states replaces rather than merges, which is real behavioral context, though it says nothing about failure or error 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?

Three short sentences: capability first, boundary second, execution precondition third. Nothing is repeated from the schema and the parenthetical workflow context is the only aside, and it earns its place.

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?

Three parameters with full schema coverage, no output schema needed, and annotations supplying the safety profile. The one thing structured data cannot express, the administrator approval gate, is stated explicitly, so an agent has everything required to call it correctly.

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 each parameter's meaning is already documented in the schema, including 'Replaces the current list' for call_states. The description's mention of 'which call states it sends' adds no meaning beyond that, so the baseline 3 applies.

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 set ('turn on or off', 'change which call states it sends') against a specific resource ('call event subscription'). The clause 'Does not change where events are sent' draws a clear boundary that separates it from sibling subscription and webhook tools.

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?

Gives a concrete use case (the N8N call-to-ticket workflow pausing and resuming) and an explicit non-use ('Does not change where events are sent'), which implicitly routes destination changes elsewhere. It stops short of naming an alternative tool outright, so a 4 rather than a 5.

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