Mailchimp MCP Server

mailchimp_lists_create

Create a Mailchimp audience to start collecting subscribers, providing contact info, campaign defaults, permission reminders, and opt-in settings.

Instructions

Create a new audience/list

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": {
      "name": "<name>",
      "contact": "<contact>",
      "permission_reminder": "<permission_reminder>",
      "campaign_defaults": "<campaign_defaults>",
      "email_type_option": "<email_type_option>"
    },
    "name": "mailchimp_lists_create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	List name
`contact`	Yes	Contact information for the list
`double_optin`	No	Enable double opt-in
`campaign_defaults`	Yes	Default campaign settings
`email_type_option`	Yes	Whether to ask subscribers for email type preference
`permission_reminder`	Yes	Permission reminder text
`marketing_permissions`	No	Enable marketing permissions (GDPR)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states the action and does not disclose idempotency, permission requirements, duplicate handling, or the response format. The mutating nature is implied by 'create' but not elaborated.

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?

The description is a single, concise sentence with no filler or redundancy. It is appropriately sized given that the schema fully documents the parameters.

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?

The description lacks any operational context such as the result of the call, potential errors, or the fact that this mutates the account. Without an output schema or annotations, an agent is left to infer the full behavior from the tool name and schema, which is incomplete.

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 has 100% description coverage, with every parameter and nested field documented. The tool description adds no additional meaning to the parameters, so it relies entirely on the schema, which warrants the baseline score of 3.

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 'Create a new audience/list' clearly states the action (create) and the resource (audience/list), which is distinct from sibling tools like update/delete/get. It clarifies that 'lists' are also called 'audiences' in Mailchimp, but otherwise adds little beyond the tool's name.

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. No exclusions, prerequisites, or context are provided. The schema lists required fields, but the description itself offers no decision framework.

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

Deploy Server