Skip to main content
Glama

Pause a WhatsApp campaign

campaign_pause
Idempotent

Pauses a running or queued WhatsApp campaign. Messages already sent stay sent; a paused campaign can be resumed later.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "campaign_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoIf true, say what would happen without pausing
campaignIdYesThe campaign's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / campaignId / description
      Previous value: -"The campaign_id from campaign_list"New value: +"The campaign's id"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare non-readonly, idempotent, non-destructive, so the safety bar is partly covered. The description adds genuinely useful behavior beyond them: already-sent messages are unaffected and the pause is reversible. It still doesn't say what happens to in-flight messages or what the call returns.

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?

Two short sentences with no filler; the core action and eligibility are front-loaded and the side-effect/reversibility note follows. Every clause carries information an agent needs.

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 simple state-change tool with full schema coverage and annotations covering the safety profile, the description supplies the essential effect and reversibility. The only gap is the absence of any statement about the response or confirmation behavior, with no output schema to fall back 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 coverage is 100%, so both campaignId and dryRun are already documented in the schema, including the dryRun semantics. The description adds no further meaning about either parameter, making the baseline 3 appropriate.

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?

The description names a specific verb and resource ('Pauses ... WhatsApp campaign') and qualifies the eligible states ('running or queued'), which distinguishes it from creation/launch siblings. It stops short of explicitly contrasting itself with any named sibling tool, so it is clear but not fully differentiated.

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?

'Running or queued' is a concrete precondition that tells the agent which campaign states this call applies to, which is real usage guidance. It does not state exclusions or point to an alternative (e.g., a resume path), so it falls short of a full when/when-not treatment.

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.