Sparetext

Stop a campaign

stop_campaign

DestructiveIdempotent

Stop a sending or paused campaign for good: its waiting texts are taken back and nobody else is texted. It can't be resumed or undone, so confirm with the user first.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	The campaign's id (cmp_…)

Output Schema

Name	Required	Description	Default
`campaign`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds real substance: pending messages are "taken back," no further recipients are texted, and the action is irreversible. That spells out the blast radius of the destruction rather than just labeling it destructive.

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, zero filler. The irreversible consequence is front-loaded and the confirmation warning lands last where it is most likely to be acted on.

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?

With an output schema present, return values need no explanation, and the description covers the remaining gaps an agent needs: eligibility, side effects on queued texts, irreversibility, and the confirmation requirement. Nothing material is missing for a single-parameter destructive tool.

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% and the single parameter documents the expected id format (cmp_…), so the schema carries the burden. The description adds no syntax, sourcing, or lookup guidance for the id beyond what is already structured, making 3 the correct baseline.

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 ("Stop a ... campaign") plus the eligible states ("sending or paused"), so an agent knows exactly what this acts on. The phrase "for good" and "can't be resumed" cleanly separate it from the sibling pause_campaign without needing to open either 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?

Gives a clear precondition for use (campaign must be sending or paused) and an explicit procedural instruction: "confirm with the user first." It stops short of naming pause_campaign or cancel_text as the alternative when the user only wants a temporary halt, leaving that inference to the agent.

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

All Sparetext 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.

Resources

Need Help?