Skip to main content
Glama

Launch approved campaign

spur_launch_campaign
Destructive

Launch the exact sequence reviewed by spur_preview_campaign. Refuses expired tokens or changed configuration, template content or audience counts. Can send and spend credits; do not automatically retry a timed-out launch.

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": {
      "confirmation_token": "<confirmation_token>",
      "confirm": "<confirm>"
    },
    "name": "spur_launch_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesSet to true ONLY after the user explicitly approved this exact action in the conversation. Never assume approval.
confirmation_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive/non-idempotent/open-world, and the description adds materially more: it can send and spend credits, it validates against expired tokens and changed configuration/template/audience counts, and it warns against retrying a timeout — a crucial disclosure given idempotentHint=false, where a retry risks duplicate sends and double spend.

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?

Three short sentences, front-loaded with what the tool does, then validation behavior, then the cost/retry warning. No filler and no repetition of the schema or annotations.

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 no output schema, the description still omits what a successful launch returns (campaign/order identifier, status) and what a refusal looks like to the caller, which matters for a destructive, non-idempotent action. The core risks — spending credits, invalidated tokens, retry hazards — are all covered, so the remaining gap is moderate rather than disqualifying.

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 50%: `confirm` is well documented in-schema, but `confirmation_token` has no description anywhere. The description hints at provenance ("the exact sequence reviewed by spur_preview_campaign") but never states that the token comes from the preview call, nor that tokens expire and are single-use — the one piece of semantics an agent most needs here.

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?

Uses a specific verb ("Launch") plus a precise scope ("the exact sequence reviewed by spur_preview_campaign"), which immediately distinguishes it from the preview sibling and from the other campaign tools. An agent knows this is the commit step of a preview-then-launch pair.

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?

Establishes a clear precondition (the sequence must have come from spur_preview_campaign) and adds an operational rule: do not automatically retry a timed-out launch. It stops short of naming the non-approval path or any alternative tool to use when the token is expired or config changed, so the agent must infer re-preview, but the context is otherwise explicit.

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