Skip to main content
Glama

Cancel scheduled campaign

campaign_cancel
Idempotent

Cancels a scheduled campaign before it starts sending. Only works while the status is scheduled; once sending has started it cannot be stopped. Uses no quota. Confirm with the person which campaign they mean (campaigns_list with status scheduled) before calling. Requires API key scope: send.

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": "campaign_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign id (a UUID), as returned by campaign_draft or campaigns_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false, destructiveHint=false, idempotentHint=true, so the safety profile is largely covered structurally. The description does add genuinely new context: quota-free operation and the required API key scope 'send', plus the state precondition. However, it says nothing about what happens to the campaign afterward (whether it returns to draft and can be rescheduled) or how an invalid-state call fails, which is the main behavioral gap for a state-transition tool.

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 sentences, front-loaded with the capability and its hard limit, then the confirmation step and the auth requirement. Every sentence carries distinct information; the only slight redundancy is repeating 'scheduled' framing already in the title.

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 one-parameter state-transition tool with full schema coverage, no output schema, and annotations covering the safety profile, this is nearly complete. The remaining omission is the post-cancel state and recovery path (reschedule via campaign_schedule), which an agent would plausibly need to act on.

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% and the single 'id' parameter is fully documented as a UUID from campaign_draft or campaigns_list, so the description adds nothing parameter-specific. Baseline 3 applies; the mention of campaigns_list is usage routing rather than parameter semantics.

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 ('Cancels a scheduled campaign') plus the scope-limiting condition ('before it starts sending'), which cleanly separates it from campaign_update, campaign_schedule, and event_cancel. An agent can pick this tool without opening the schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use ('Only works while the status is scheduled'), explicit when-not ('once sending has started it cannot be stopped'), and a concrete prerequisite workflow: confirm the target with the person using campaigns_list with status scheduled before calling.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources