Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by AlexlaGuardia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

replicate_campaign

Duplicate an existing campaign to create a copy, returning the new campaign ID for editing and scheduling.

Instructions

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

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": "replicate_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided, and the description only mentions returning a new campaign ID. It does not disclose behavioral traits such as side effects, what gets copied, or any limitations, leaving the agent with insufficient insight.

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 very concise at one sentence and front-loads the key action. However, it is too brief and omits important details, balancing efficiency with completeness.

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 complexity of replicating a campaign and the absence of annotations or output schema, the description is incomplete. It lacks information on what is copied, prerequisites, or expected behavior beyond the ID return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description adds no meaning to the campaign_id parameter beyond what the schema already provides (type string, required). The description should explain the parameter's purpose or constraints but does not.

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 explicitly states 'Create a copy of an existing campaign' with a clear verb and resource, and it distinguishes from siblings like create_campaign by specifying duplication rather than original creation.

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 replicate_campaign vs alternatives like create_campaign. The description lacks context on prerequisites or scenarios where copying is appropriate.

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