Mailchimp MCP Server

mailchimp_lists_list

Retrieve all Mailchimp lists and audiences with optional filters for email, creation dates, sorting, and pagination to manage your audience data effectively.

Instructions

Get all lists/audiences in your Mailchimp account

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mailchimp_lists_list"
  }
}

Input Schema

Name	Required	Description
`count`	No	Number of records to return
`email`	No	Filter by subscriber email
`offset`	No	Number of records to skip
`sort_dir`	No	Sort direction
`sort_field`	No	Sort field
`since_date_created`	No	Return lists created after this date (ISO 8601)
`before_date_created`	No	Return lists created before this date (ISO 8601)

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?

With no annotations, the description carries the full burden of behavioral disclosure, but it merely says 'Get all lists/audiences.' It fails to mention that the result is likely paginated with count/offset parameters, that 'all' may be limited by defaults, or that filtering by email/date is possible. The description is too sparse to set expectations.

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, direct sentence with no unnecessary words. It is immediately readable and front-loaded with the action and object.

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?

For a list endpoint with 7 parameters and no output schema, the description does not explain pagination behavior, default limits, available filters, or the structure of the returned data. This makes the tool incomplete for an agent that must predict response formatting or handle large result sets.

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 already describes all 7 parameters (100% coverage), so the description does not need to add parameter details. However, the description adds no extra semantic value beyond what the schema provides, meeting the baseline for schema-covered parameters.

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 ('Get') and the resource ('all lists/audiences'), making the tool's basic purpose unambiguous. However, it does not differentiate this from sibling tools like mailchimp_lists_get or mailchimp_audiences_get_stats, relying on the name to imply listing functionality.

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 on when to use this tool versus alternatives such as mailchimp_lists_get for a single list or mailchimp_audiences_get_stats for statistics. There is no mention of filtering, pagination, or typical use cases, leaving the agent without decision support.

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

Deploy Server