Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_audiences

Read-only

List all audiences with subscriber counts, open/click rates, and opt-in settings. Obtain list IDs and audience details in a single request.

Instructions

List audiences (lists) with subscriber counts and engagement rates.

First step in most workflows to discover list_id values. Use get_audience_details for full stats of a known audience. Use search_members to find a specific member.

Args: count: Audiences to return (1-1000, default 10). Most accounts have fewer than 10. offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and audiences array. Each: id (use as list_id), name, member_count, unsubscribe_count, open_rate (0-1), click_rate (0-1), date_created, and the audience settings carried in the same list payload: campaign_defaults (default from_name, from_email, subject, language), double_optin (bool: true = confirmed/double opt-in), marketing_permissions (bool: GDPR permission fields enabled). These settings come free with this call -- the /lists endpoint returns each list's full object -- so all audiences and their opt-in/sender/compliance config are available in one request, without a get_audience_details call per audience.

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
accountNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations readOnlyHint already indicate safety. Description adds pagination behavior, return structure, and the fact that full audience settings are returned, providing useful behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with summary, usage, Args, Returns. The Returns section is verbose but informative. Front-loaded with key information.

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?

Covers purpose, usage, parameters (mostly), and return format. Minor gap with the undocumented account parameter. Overall comprehensive for a read-only list tool.

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?

Explains count and offset well with ranges and usage, but omits the account parameter entirely. Schema coverage was 0%, so description compensates partially but not fully.

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?

Clearly states it lists audiences with subscriber counts and engagement rates. Explicitly distinguishes from get_audience_details and search_members, providing sibling differentiation.

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

Usage Guidelines5/5

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

Describes it as the first step in most workflows to discover list_id values, and gives explicit when-to-use cues for alternatives like get_audience_details and search_members.

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