Mailchimp MCP Server

mailchimp_audiences_create_segment

Create a new segment for a Mailchimp list by setting conditions for a saved segment or providing email addresses for a static segment.

Instructions

Create a new saved or static segment for a 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": {
      "list_id": "<list_id>",
      "name": "<name>"
    },
    "name": "mailchimp_audiences_create_segment"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Segment name
`list_id`	Yes	List/audience ID
`options`	No	Conditions for a saved segment (use instead of static_segment)
`static_segment`	No	Email addresses for a static segment

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden. It only says 'create' which implies a write operation, but does not disclose behavioral traits such as permissions, idempotency, or the distinction between saved and static segment handling. The description is not contradictory but is minimal.

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 that is front-loaded with the verb and resource. No unnecessary words.

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?

The description is adequately clear for a simple create operation, but given the absence of annotations and the presence of sibling tools, it would benefit from clarifying when to use this over lists_create_segment. The schema covers parameter details, but the overall context is not fully complete.

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?

Schema coverage is 100%, so the baseline is 3. The description mentions 'saved or static' which maps to the options and static_segment parameters, but the schema already provides richer descriptions. The description adds little value beyond what the schema defines.

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 a new saved or static segment for a list' with a specific resource and type. It distinguishes from update/delete/get tools but does not explicitly differentiate from the sibling mailchimp_lists_create_segment, which appears to serve the same purpose.

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 is provided about when to use this tool versus alternatives, nor about choosing saved vs static segments. It only implies that the tool creates segments; there is no mention of prerequisites or exclusions.

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

Deploy Server