Skip to main content
Glama

Review campaign before launch

spur_preview_campaign
Read-onlyIdempotent

Review current configuration, channel content, recipient count and billing. Mail-containing sequences show sample postcard artwork and clear zones. Returns a 30-minute token bound to the campaign, channel templates and mail return address. Nothing launches.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "spur_preview_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that a 30-minute token is returned, what it is bound to (campaign, channel templates, mail return address), and that nothing is launched or mutated. The annotations already cover read-only/idempotent safety, so this additional return-contract detail is genuine added value, though token expiry/refresh behavior is left implicit.

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 short, front-loaded sentences with no filler; the critical constraint ("Nothing launches") is placed last for emphasis and the return value is described compactly. Slightly telegraphic phrasing such as "clear zones" and "mail return address" assumes domain familiarity.

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?

With only one parameter and no output schema, the description carries the right load: it explains what is inspected and summarizes the returned object's scope and lifetime. The remaining gap is how campaign_id is sourced and whether the token must be passed to spur_launch_campaign.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description never mentions campaign_id's format, where to obtain it, or what the token is scoped to at the identifier level. The single required parameter is inferable from the tool's purpose, but the description does essentially nothing to compensate for the empty schema.

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?

States a specific verb+resource (review the current campaign configuration) and enumerates what is checked: channel content, recipient count, billing, plus artwork and clear zones for mail sequences. It clearly distinguishes itself from launch siblings via "Nothing launches," though it never names the channel-specific preview siblings it presumably supersedes.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase "Nothing launches" and the title "Review campaign before launch" signal a pre-launch dry run. There is no explicit statement of when to prefer this over spur_preview_mail_campaign or spur_preview_postcard_campaign, and no stated preconditions or exclusions.

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