Mailchimp MCP Server

mailchimp_campaigns_create

Create a new email campaign by specifying its type, recipient list, and settings like subject line, from name, and reply-to address.

Instructions

Create a new 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": {
      "type": "<type>",
      "recipients": "<recipients>",
      "settings": "<settings>"
    },
    "name": "mailchimp_campaigns_create"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Campaign type
`settings`	Yes	Campaign settings
`recipients`	Yes	Campaign recipients settings

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Create a new campaign'. It does not state whether the campaign is created as a draft, whether it causes any immediate sending, what permissions are needed, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence that essentially restates the tool name without adding specifics. While not verbose, it is under-specified and fails to convey necessary context, so it does not earn its place.

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's complexity—nested objects, multiple required fields, and no output schema—the description is severely incomplete. It does not explain the creation flow, the significance of the 'type' enum, or what happens after creation, leaving the agent with insufficient guidance.

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 input schema provides 100% coverage of parameter descriptions, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already documents, so it does not exceed the baseline.

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 action (create) and resource (a new campaign), which distinguishes it from sibling tools like update, delete, or send. However, it lacks scope details such as 'creates a draft campaign' or 'does not send', which would make it fully specific.

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. It does not mention that this is for creating a draft that will later need to be sent or scheduled, nor does it reference sibling tools like mailchimp_campaigns_update or mailchimp_campaigns_send.

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

Deploy Server