Skip to main content
Glama

Run the content swarm

execute_content_plan

Execute a linked content plan through the real content swarm: planner brief, copy, image, video storyboard, email and compliance review. This spends AI credits and creates draft/approved assets; it does not 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": {
      "plan_id": "<plan_id>"
    },
    "name": "execute_content_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe content plan to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover readOnly/idempotent/destructive, so the description earns real credit for disclosing that this spends AI credits and produces draft/approved assets rather than published output. It stops short of saying whether re-invoking the same plan_id duplicates work or how long the swarm run takes, which matters given idempotentHint=false.

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?

Two sentences, both load-bearing: the first names the operation and its outputs, the second front-loads the cost warning and the publish exclusion. No filler or restatement of the tool name.

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, non-idempotent execution tool with no output schema, the definition covers cost, side effects, and scope boundaries well. The remaining gap is what happens after the call — whether results are returned inline or must be fetched via get_swarm_activity — which an agent would want before committing credits.

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?

There is only one parameter at 100% schema description coverage, so the schema already defines plan_id fully. The description adds only the qualifier 'linked,' hinting the plan must already exist, which is marginal value over the structured field.

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?

States a specific verb ('Execute') plus resource ('a linked content plan') and then enumerates the pipeline stages produced (planner brief, copy, image, video storyboard, email, compliance review). This is concrete enough to distinguish it from siblings like start_planner_campaign or retry_planner_stage without opening any schema.

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 closing clause 'it does not publish anything' gives an explicit scope boundary that rules out a publishing use case. However, it never states when to pick this over start_planner_campaign or retry_planner_stage, nor any prerequisite such as the plan needing to exist or be in a ready state.

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