Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by AlexlaGuardia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_audiences

List all Mailchimp mailing lists with subscriber counts and statistics, supporting pagination via count and offset parameters.

Instructions

List all audiences (mailing lists) with subscriber counts and 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
countNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It mentions listing with subscriber counts and stats, but does not disclose pagination behavior (e.g., default limit of 20 per page), potential limits, or any other behavioral traits. The output schema covers return values, but the description adds minimal behavioral detail.

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 sentence that is direct and lean. Every word is informative, with no unnecessary detail or repetition.

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?

Given the presence of an output schema (covering return values) and simple parameters (0 required), the description is moderately complete. However, it lacks context on pagination behavior and what 'stats' includes, which would be beneficial for an agent selecting this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds no meaning to the parameters ('count', 'offset'). It does not explain their purpose, defaults, or how they control pagination. The schema provides defaults and titles, but the description offers no additional value.

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 verb 'List', the resource 'audiences (mailing lists)', and the additional info 'with subscriber counts and stats'. This clearly distinguishes it from sibling tools like 'get_audience' (single audience), 'create_audience', etc.

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 description provides no explicit guidance on when to use this tool versus alternatives. However, as a standard list operation, its purpose is self-evident among siblings focused on different resources or actions. Implicit usage is clear but not explicitly stated.

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