Skip to main content
Glama
Sign In

Mailercloud

by com.mailercloud.mcp
OverviewDiscussionsAdmin

Clone Template

clone_template

Copy an existing template under a new name: same content, category and editor, so a drag-and-drop template stays editable in the drag-and-drop editor. The original is not changed. Needs template_id. Set dry_run: true to see the copy's name without creating it.

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": {
      "template_id": "<template_id>"
    },
    "name": "clone_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName for the copy (default: the original name followed by (Copy))
dry_runNoShow what would be created without creating anything
template_idYesID of the template to copy (from list_templates)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the annotations: the original is left unmodified (reinforcing destructiveHint=false), the copy inherits content/category/editor, and dry_run reveals the resulting name. It stays silent on the fact that repeated calls create additional copies (relevant given idempotentHint=false) and on any permission or naming-collision behavior.

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?

Four short, front-loaded sentences with the core action first and preview/dry-run guidance last. The sentence 'Needs template_id' is the only clear redundancy, since the schema already marks it required.

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 three-parameter mutation tool with no output schema but full annotation coverage, the description covers the essentials: what is copied, that the source is untouched, and a safe preview path. Minor gaps remain around what the response contains (the new template's ID) and duplicate-call behavior.

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%, so all three parameters are already documented, including the (Copy) default naming. The description's 'Needs template_id' merely restates the required field, and its dry_run note slightly expands what the schema says but adds no new syntax or format detail. Baseline 3 is warranted.

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?

States a specific verb and resource ('Copy an existing template under a new name') and adds what is carried over (content, category, editor), which distinguishes it from create_template and create_dnd_email_template. It does not name a sibling alternative explicitly, so an agent must infer the boundary rather than being told.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: clone when you want the original's content preserved, and use dry_run to preview first. There is no explicit 'use create_template instead if starting from scratch', and no statement of prerequisites (e.g., that the template must be DnD-editable) beyond the passing mention of the drag-and-drop editor.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mailercloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources