Skip to main content
Glama

Copy an A/B variant

copy_campaign_step_variant
DestructiveIdempotent

Use this when the user wants both variants of an A/B split to start from the same steps, so that one thing can be changed and compared. Replaces the steps of one variant with copies of the other's; the steps it replaces are gone. stepId is the split step. 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>",
      "stepId": "<stepId>",
      "fromBranchKey": "<fromBranchKey>",
      "toBranchKey": "<toBranchKey>"
    },
    "name": "copy_campaign_step_variant"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepIdYesThe step's id, as the campaign's steps list gives it.
campaignIdYesThe campaign's id.
toBranchKeyYesThe other variant, whose steps the copies replace.
fromBranchKeyYesThe variant to copy: `a` or `b`.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description reinforces this with 'the steps it replaces are gone' — an explicit statement of what data is lost. It also adds cost information ('Free') that annotations do not carry, which matters for a mutation. It does not cover what happens if the branch keys are identical or whether the copy preserves step IDs, keeping it below a 5.

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

Conciseness4/5

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

Three compact clauses: trigger condition first, then mechanics, then the role of stepId, with the cost note trailing. Front-loading the 'when' is effective, though the closing 'Free.' is a bare fragment whose meaning (no credit cost) has to be inferred.

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 four-required-parameter destructive mutation with no output schema, the description covers purpose, trigger, data-loss consequence, the key parameter's special constraint, and cost. Nothing an agent needs 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description goes beyond it by clarifying that stepId must be the split step, which the schema only calls 'The step's id'. The from/to branch semantics are already fully documented by the schema enum descriptions, so that part earns no extra credit.

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+resource — copying the steps of one A/B branch over the other — and explicitly frames the operation around the split step ('stepId is the split step'), which separates it from generic step tools like update_campaign_step or duplicate_campaign. An agent can tell exactly what this does without opening the 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?

'Use this when the user wants both variants of an A/B split to start from the same steps, so that one thing can be changed and compared' gives a clear, concrete trigger condition tied to the A/B testing workflow. It stops short of naming alternatives (e.g., when to re-create steps manually vs. copy them) or stating exclusions, so it falls short of 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