Skip to main content
Glama

List strategy campaigns

list_planner_campaigns
Read-onlyIdempotent

The 12-stage Campaign Studio strategy runs in this workspace, with status and current stage. Read this before creating content so the plan is linked to a real strategy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_planner_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds that results carry status and a current stage across a 12-stage model, which is useful framing, but says nothing about pagination, ordering, or what happens when the workspace has no strategy.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Only two sentences, but the opening is garbled ('The 12-stage Campaign Studio strategy runs in this workspace, with status and current stage') and does not front-load what the tool actually does. The key purpose has to be inferred from the second sentence rather than stated up front.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with one optional parameter and no output schema, the definition should at minimum state that it returns a list of campaigns and how limit affects the result. Neither is present, and the relationship to get_planner_campaign and list_plans is left unexplained.

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% for the single 'limit' parameter, so the description is the only place semantics could be supplied, and it never mentions limit at all. The schema's type/default/min/max make the parameter guessable, but the description does nothing to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('the 12-stage Campaign Studio strategy') and says it carries status and current stage, but never states the action verb 'list' or whether it returns one strategy or many campaigns. It does not differentiate itself from the sibling get_planner_campaign, which plausibly retrieves a single strategy.

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?

It gives one concrete usage cue: read this before creating content so the plan is linked to a real strategy. There is no guidance on when not to use it, no mention of get_planner_campaign as an alternative, and no note about how limit/ordering affects usage.

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