Skip to main content
Glama

Save a campaign as a template

save_campaign_as_template

Use this when the user wants to reuse a campaign's sequence later. Keeps the campaign's steps and schedule (sending days, hours, time zone and lists) as a named template that new campaigns can start from. The campaign itself does not change. Free. Calling again saves another template.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe template's name.
campaignIdYesThe campaign whose steps and schedule (sending days, hours, time zone and lists) the template keeps.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare non-read-only, non-destructive, non-idempotent, closed-world behavior, and the description adds real context on top: the source campaign is unchanged, the operation is free, and repeated calls create additional templates (explaining why idempotentHint is false in practical terms). It does not cover permission requirements, whether duplicate template names are allowed, or any cap on templates, so it falls short of 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.

Conciseness5/5

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

The usage condition is front-loaded in the first sentence, followed by what is captured, then three short facts (source unchanged, free, repeat calls stack). Every sentence carries information an agent would otherwise have to guess, and there is no padding.

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 two-parameter creation tool with full schema coverage and no output schema, the description covers side effects, cost, and duplication semantics well. The one remaining gap is that it never says what comes back (presumably a template identifier or name) which the agent would need to reference the new template later.

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 coverage is 100%: both parameters carry descriptions, examples, and constraints (24-char hex pattern for campaignId, 1-200 chars for name). The description's parenthetical about what the template keeps largely restates the campaignId schema text, so it adds little meaning beyond what the schema already provides; 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 ('save ... as a named template') and scopes exactly what is captured: steps plus schedule (sending days, hours, time zone and lists). It also explicitly rules out the neighboring interpretation that the source campaign is modified, which separates it from mutation siblings like update_campaign.

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 a clear trigger condition: 'Use this when the user wants to reuse a campaign's sequence later.' That is genuine when-to-use guidance rather than implication. It stops short of naming alternatives (e.g., list_campaign_templates or delete_campaign_template) or stating any when-not conditions such as template-count limits.

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