Skip to main content
Glama

replicate_campaign

Create a copy of an existing Mailchimp campaign to reuse content and settings for new marketing initiatives.

Instructions

Create a copy of an existing campaign. Returns the new campaign ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `replicate_campaign` tool handler is defined in `mcp_mailchimp/server.py` as an asynchronous function decorated with `@mcp.tool()`. It uses the `MailchimpClient` to send a POST request to the Mailchimp API to duplicate a campaign.
    async def replicate_campaign(campaign_id: str) -> str:
        """Create a copy of an existing campaign. Returns the new campaign ID."""
        mc = get_client()
        c = await mc.post(f"/campaigns/{campaign_id}/actions/replicate")
        return _fmt({
            "new_campaign_id": c["id"],
            "original_campaign_id": campaign_id,
            "status": c.get("status", ""),
            "message": "Campaign replicated.",
        })
Behavior2/5

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

No annotations are provided, so the description carries full burden. It mentions the action ('Create a copy') and return value ('Returns the new campaign ID'), but lacks critical behavioral details like whether this requires specific permissions, if the copy includes all settings/content, what happens to the original campaign, or any rate limits. For a mutation tool with zero annotation coverage, this is insufficient.

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?

Two sentences with zero waste: the first states the action, the second states the return value. It's front-loaded and efficiently communicates the core purpose without unnecessary details.

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

Completeness3/5

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

Given the tool has an output schema (which likely covers the return value), the description doesn't need to explain returns in detail. However, as a mutation tool with no annotations and incomplete behavioral transparency, it should provide more context about permissions, side effects, or what gets copied. It's minimally adequate but has clear gaps.

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 description coverage is 0%, so the description must compensate. It doesn't explicitly mention the 'campaign_id' parameter, but the phrase 'of an existing campaign' strongly implies the need for an identifier. Since there's only one parameter, this is adequate, though adding a brief note about the parameter would improve clarity.

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 clearly states the verb ('Create a copy') and resource ('of an existing campaign'), and distinguishes it from siblings like 'create_campaign' (which creates new from scratch) and 'update_campaign' (which modifies existing). It specifies the exact operation without ambiguity.

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?

The description implies usage when you need to duplicate an existing campaign, but doesn't explicitly state when to use this versus alternatives like 'create_campaign' for new campaigns or 'update_campaign' for modifications. No prerequisites or exclusions are mentioned, leaving some context gaps.

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/AlexlaGuardia/mcp-mailchimp'

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