CallMCP — Phone Call MCP Server

Cancel Email Campaign

cancel_email_campaign

DestructiveIdempotent

Stop an email campaign so nothing more is sent from it. Emails already delivered stay delivered. Needs campaign_id and the fingerprint of its current revision. Business owner only.

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": {
      "business_id": "<business_id>",
      "campaign_id": "<campaign_id>",
      "fingerprint": "<fingerprint>"
    },
    "name": "cancel_email_campaign"
  }
}

Input Schema

Name	Required	Description
`business_id`	Yes	The business that sends the email.
`campaign_id`	Yes	The campaign to stop.
`fingerprint`	Yes	Fingerprint of its current revision, from get_email_campaign.

Output Schema

Name	Required	Description
`id`	No
`code`	No
`error`	No	Present when success is false
`action`	No
`status`	No
`success`	Yes	Whether the tool completed successfully
`senderId`	No
`fingerprint`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds value by defining the partial-effect boundary ("Emails already delivered stay delivered") and the permission requirement, plus the revision-fingerprint precondition that guards against stale state. It does not say whether a cancel can be reversed or how in-flight sends behave.

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?

Four short sentences, front-loaded with the effect, then the caveat, then the requirements. Every sentence carries information an agent needs; nothing is redundant.

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?

An output schema exists, so return values need not be explained, and the description covers effect, authorization, and the state prerequisite. It leaves unstated how an agent should handle a stale fingerprint or verify business-owner status, which would be the remaining gap.

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 three parameters are already documented. The description only restates campaign_id and reframes fingerprint as "the fingerprint of its current revision"; the real added meaning (concurrency guard) is marginal and the schema already points to get_email_campaign.

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 ("Stop an email campaign") and clarifies the scope of the effect ("nothing more is sent from it"). It does not explicitly contrast with a pause or sibling lifecycle tool, but the effect is unambiguous.

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 concrete prerequisites ("Needs campaign_id and the fingerprint of its current revision") and an authorization constraint ("Business owner only"). It stops short of naming when to prefer this over an alternative such as pausing or drafting, so it lacks explicit exclusions.

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

All CallMCP — Phone Call MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.