Skip to main content
Glama

Campaign drafts, recipients and runs

spur_manage_campaign
Destructive

Create/update/delete a campaign draft, inspect a campaign/runs, stage consenting recipients respecting opt-outs, cancel, or retry failed runs. Launch requires a separate preview token. Retrying can send and needs approval.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety bar is partly covered. The description adds useful context beyond annotations: staging respects opt-outs, retry can send, retry needs approval, and launch is separated behind a preview token.

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?

The description is two dense sentences, front-loads the action set, and then adds the most important safety/precondition notes. There is no wasted wording.

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?

This is a complex multi-action tool with destructive and open-world annotations, and the description covers all action categories plus approval and launch-precondition caveats. It does not describe return values or pagination, but no output schema exists and the input schema covers those details.

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%, so the schema already documents parameters including confirm and pagination fields. The description maps action names to purposes but adds little parameter-level meaning beyond what the schema provides.

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?

The description uses specific verbs and resources: create/update/delete draft, inspect campaign/runs, stage recipients, cancel, and retry failed runs. It also distinguishes launch by stating that launch requires a separate preview token, which helps separate this tool from preview/launch siblings.

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 description gives clear conditions for key paths: launch needs a separate preview token, and retrying can send and needs approval. It does not explicitly name the preview/launch sibling tools, but the required precondition is sufficient to guide selection.

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