Skip to main content
Glama

Start a strategy campaign

start_planner_campaign

Start the 12 stages for an existing draft. This spends model tokens. It does not approve a stage, bypass the quality gate, or publish anything.

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

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description adds genuinely useful context beyond that: the call consumes model tokens (a real cost signal) and it explicitly does not approve a stage, bypass the quality gate, or publish content. It leaves the non-idempotency consequence unstated — what happens if it is started twice on the same draft is not addressed.

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, zero filler, with the action and cost warning front-loaded and the boundary conditions following. Every clause carries distinct information.

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 one-parameter mutation with no output schema, the description covers the action, the cost, and the guardrails, which is close to sufficient. What remains missing is the outcome shape (are the 12 stages started synchronously? what is returned?) and the non-idempotent retry implication.

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 0% for the single campaign_id parameter, so the description must compensate. It does add meaning by indicating the id refers to an existing draft campaign, but it says nothing about format, where to obtain the id (e.g., list_planner_campaigns), or validation beyond minLength 1.

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?

The description states a specific verb and scope: 'Start the 12 stages for an existing draft.' Combined with the title and the 'existing draft' qualifier, an agent can tell this acts on a pre-created campaign rather than creating one (create_planner_campaign). It stops short of naming the sibling it pairs with, so the differentiation is inferred rather than explicit.

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?

'for an existing draft' implies the prerequisite (a draft campaign must already exist) and the negative clauses clarify what the tool will not do, which steers an agent away from expecting approval or publishing. However, there is no explicit statement of when to choose this over create_planner_campaign or retry_planner_stage, so the routing guidance is only implied.

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