Skip to main content
Glama

Rewrite a campaign's AI steps

regenerate_campaign_steps
Destructive

Use this when the user wants every AI-written step of a campaign rewritten from its knowledge hub, for example after the hub changed. The topics of all AI steps are replaced; messages already queued keep what they say. It can take a minute. Free.

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": {
      "campaignId": "<campaignId>"
    },
    "name": "regenerate_campaign_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior5/5

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

The annotations already declare destructiveHint=true, idempotentHint=false, so the safety profile is known; the description then adds real substance on top: what exactly is overwritten (the topics of ALL AI steps), what survives (already-queued messages keep their content), latency ("can take a minute"), and price ("Free"). That is precisely the kind of impact and cost disclosure an agent needs before firing a destructive call.

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?

Four short sentences: trigger, effect, side effect, cost. Every sentence carries distinct information with no repetition, and the use condition is front-loaded.

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

Completeness5/5

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

For a destructive, non-idempotent mutation with no output schema and one fully documented parameter, the description covers rationale, blast radius, message preservation, runtime, and cost. Nothing needed to call it safely is missing.

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 a single parameter and the schema already documents it at 100% coverage, including the 24-character hex pattern, so the schema carries the meaning. The description adds nothing about campaignId and the baseline of 3 is appropriate.

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 gives a specific verb and resource combo ("every AI-written step of a campaign rewritten from its knowledge hub") plus a precise scope, so an agent knows this is a bulk rewrite of AI-generated step content, not a single-step edit. It falls short of a 5 only because it never names a sibling tool (e.g. update_campaign_step or regenerate_knowledge_hub_page) to make the boundary explicit.

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?

"Use this when the user wants every AI-written step of a campaign rewritten... for example after the hub changed" gives an explicit triggering condition and a concrete scenario. There is no "when not to use" clause or named alternative for the single-step or hub-page cases, which keeps it below a 5.

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