Skip to main content
Glama

Pause a campaign

pause_campaign
DestructiveIdempotent

Use this when the user wants a campaign to stop sending for now. Its queued messages wait, and go out if it is launched again. Refused while a launch or pause of the same campaign is still running. Free.

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

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations it discloses three behaviors the agent could not otherwise know: queued messages are held and resume on relaunch (reversibility), the call is refused while a launch or pause of the same campaign is in flight (concurrency conflict), and it costs nothing. That is exactly the kind of operational context annotations cannot carry, and it is more specific than the generic destructiveHint=true.

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 usage trigger, then the side effect, the failure condition, and the cost. Nothing is redundant and each sentence carries a distinct fact.

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 single-parameter mutation with annotations and no output schema, this covers intent, side effects, conflict behavior, and cost. The only mild gap is what the caller observes on success (the returned campaign state), which the missing output schema leaves undocumented.

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 the single parameter's meaning and format (24-char hex campaignId) are fully documented in the schema. The description adds no parameter-level detail, which is acceptable at this coverage level but is not value beyond the structured data.

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 (pause a campaign) and immediately pins down the semantics that distinguish it from a stop or delete: sending stops 'for now' while queued messages are preserved. An agent can tell this apart from terminal operations such as stop or delete without consulting any schema.

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?

The opening clause 'Use this when the user wants a campaign to stop sending for now' gives an explicit triggering condition, and the queued-message behavior clarifies the intended intent. It does not name an alternative for permanent stopping, so routing between pause and stop/delete is only implied by the contrast rather than stated outright.

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