Skip to main content
Glama
Sign In
mailchimp-mcp

mailchimp-mcp

by livemau5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_audiences

Fetch all Mailchimp audiences and lists, showing subscriber counts and key statistics for each. Get a clear overview of your audience data at a glance.

Instructions

List all audiences (lists) with subscriber counts and key stats.

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

Input Schema

NameRequiredDescriptionDefault
countNoNumber of audiences to return (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry full behavioral disclosure. It mentions output fields but omits critical behavior such as default/maximum count, pagination, ordering, or whether 'all' is truly all given the count parameter. The phrase 'List all audiences' is potentially misleading when paired with a limit parameter.

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 one concise sentence that states the action, resource, and output highlights. No wasted words or redundant repetition of the schema.

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?

For a simple list tool, the description plus schema provide reasonable coverage, but the lack of an output schema and the ambiguity around 'all' vs. the count parameter leave gaps. The description doesn't clarify what 'key stats' includes or how results are limited, making it incomplete for an agent needing precise return expectations.

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 single 'count' parameter is fully described in the schema (default 10, max 100), so schema coverage is 100%. The description does not add any additional meaning about the parameter, staying at the baseline for schema-backed clarity.

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 uses a specific verb ('List') and resource ('audiences'), clarifying the scope ('all audiences') and adding detail about output content ('subscriber counts and key stats'). This clearly distinguishes it from sibling tools like list_campaigns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context of when to use this tool is implied—when you need audience lists with statistics—but there are no explicit exclusions or comparisons to alternative tools. No mention of when to prefer search_members or search instead.

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

Deploy Server

Other Tools