Mailchimp MCP Server

mailchimp_audiences_get_stats

Retrieve detailed statistics for a specific audience, including subscriber counts, open/click rates, and growth data.

Instructions

Get detailed statistics for a specific audience/list including subscriber counts, open/click rates, and growth data

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

Input Schema

Name	Required	Description	Default
`list_id`	Yes	List/audience ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of transparency. It appropriately indicates a read operation through 'Get' and lists the types of data returned, but it does not disclose any potential limitations like time periods or whether the stats are all-time or recent, nor does it mention required permissions.

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, tightly worded sentence that front-loads the action and resource. Every word earns its place, with no redundant or generic filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool, the description provides the essential information: what it does and the categories of data it returns. However, it does not describe the return format or any filters (e.g., date ranges), and the lack of alternative guidance makes it slightly incomplete for an agent navigating the many sibling tools.

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 fully documents list_id with 'List/audience ID', so the description adds no additional parameter semantics. Since schema coverage is 100%, the baseline of 3 applies; the description does not repeat or enrich parameter details.

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 clearly states the tool retrieves detailed statistics for a specific audience/list, enumerating subscriber counts, open/click rates, and growth data. The verb 'Get' and resource 'specific audience/list' make the purpose unmistakable, and the listed data types help distinguish it from simple list-getting tools.

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 related tools such as mailchimp_reports_get for campaign-specific stats or mailchimp_audiences_get_growth_history for growth-only data. The description only implies usage via the purpose, offering no exclusions or alternatives.

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

Deploy Server