Skip to main content
Glama

clone_campaign

Duplicate a Mautic campaign by providing its ID to create an identical copy for reuse.

Instructions

Clone an existing campaign (Mautic 7)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaignIdYesID of the campaign to clone
Behavior2/5

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

No annotations provided, so description carries full burden. It only says 'clone' without explaining what gets cloned (settings, contacts?), side effects, or whether it creates a new campaign ID. Minimal behavioral disclosure.

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?

Single sentence, no wasted words, front-loaded with action and resource.

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

Completeness2/5

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

Simple tool with one parameter, but no output schema and description lacks return value indication (e.g., cloned campaign ID), permissions, or side effects. Incomplete for a mutation tool.

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% with one parameter described. The description adds no meaning beyond the schema—it just restates 'clone an existing campaign'. Baseline 3 is appropriate as schema does the work.

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 'Clone an existing campaign (Mautic 7)' clearly states the action (clone) and resource (existing campaign), with a version hint, distinguishing it from related tools like create_campaign or export_campaign.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives (e.g., create_campaign), no prerequisites mentioned, and no context about when cloning is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Cbrown35/mantic-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server