Skip to main content
Glama

Duplicate a campaign

duplicate_campaign

Use this when the user wants a copy of a campaign to change or to run again. Makes a new draft with the original's settings and steps, named "Copy of" and the original's name. Nobody is enrolled in the copy until it is launched. Free. Calling again makes another copy.

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

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, it discloses the resulting state (a draft, not a live campaign), the naming convention (“Copy of” + original name), the enrollment guarantee (“Nobody is enrolled in the copy until it is launched”), the cost (“Free”), and the non-idempotent retry behavior — all facts an agent cannot derive from readOnlyHint/idempotentHint/destructiveHint alone.

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, front-loaded with the when-to-use condition, followed by result, side effects, cost, and repeat-call behavior. Nothing is redundant with the title and no sentence could be dropped without losing 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 tool with no output schema and full annotation coverage, the description covers trigger, outcome, naming, enrollment, cost, and idempotency. The only meaningful gap is that with no output schema it never says what is returned (e.g., the new campaign's id), which an agent needs for follow-up calls.

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 description coverage is 100% (campaignId is documented with its 24-char hex pattern and length), so the schema carries parameter semantics. The description adds no extra meaning about the id — no note about where to obtain it or what happens if it is invalid — so the baseline 3 applies.

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?

The description names a specific verb and resource (“Makes a new draft with the original's settings and steps”) and immediately distinguishes duplication from creating a campaign from scratch by anchoring on “a copy of a campaign.” An agent can tell this apart from create_campaign or save_campaign_as_template 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?

It gives an explicit trigger (“Use this when the user wants a copy of a campaign to change or to run again”) that maps copy-intent to this tool, and “Calling again makes another copy” implicitly warns against retry loops. It stops short of naming a concrete alternative (e.g., save_campaign_as_template for reusable templates) or stating when not to duplicate.

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