Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_campaigns_replicate

Duplicate a Mailchimp campaign using its campaign ID. Create an exact copy to reuse, modify, or test variations without starting from scratch.

Instructions

Replicate (duplicate) a campaign

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "mailchimp_campaigns_replicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesCampaign ID to replicate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full behavioral disclosure burden. It only states the action without explaining what replication entails (e.g., whether it creates a new campaign, copies all settings, or has any side effects). This lack of transparency is a significant gap for a tool that presumably creates a new resource.

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?

The description is extremely concise, using a single phrase that directly states the purpose. While it is not verbose, it lacks any structure or additional details that could enhance clarity. It is appropriately sized for a simple one-parameter tool but does not fully capitalize on the opportunity to provide more context.

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?

Given the tool has only one parameter and no annotations or output schema, the description is still too sparse. It does not explain what 'replicate' means in the Mailchimp context (e.g., creating a new campaign with identical settings), nor does it mention any prerequisites or side effects. The description is minimally viable but leaves the agent uncertain about the full scope of the operation.

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?

The schema fully describes the only parameter 'campaign_id' with the description 'Campaign ID to replicate', which matches the tool description. Since schema coverage is 100%, the description adds no additional meaning, but the baseline of 3 is appropriate because the schema already handles parameter semantics.

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?

The description clearly states the verb 'replicate' (with 'duplicate' as a synonym) and the resource 'campaign'. It accurately conveys the core action and is not a mere tautology, though it does not differentiate from related sibling tools like 'create' or 'update'.

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?

There is no guidance on when to use this tool versus alternatives such as 'create' or 'copy'. The description provides no context about the appropriate scenario for replication, leaving the agent to infer usage from the name alone.

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

Deploy Server

Other Tools