Skip to main content
Glama
damientilman

Mailchimp MCP

list_audience_members

Read-only

Retrieve members of a Mailchimp audience with their subscription status, merge fields, open and click rates. Filter by status for targeted lists.

Instructions

List members of a specific audience with subscription status, merge fields, and engagement stats.

Use to browse members of a known audience. Use search_members instead to find a specific person by email or name across all audiences. Use list_segment_members to list members of a specific segment/tag.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. count: Number of members to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count. status: Filter by subscription status. Valid values: 'subscribed', 'unsubscribed', 'cleaned', 'pending', 'transactional'. Omit to return all statuses.

Returns: JSON with total_items and members array. Each member: id (MD5 hash of email), email_address, status, full_name, merge_fields (object with FNAME, LNAME, etc.), open_rate (decimal 0-1), click_rate (decimal 0-1), timestamp_opt (ISO 8601 opt-in time).

Example: list_audience_members(list_id="abc123", count=50, status="subscribed") -> {"total_items": 5000, "members": [{"email_address": "jane@co.com", "status": "subscribed", ...}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo
statusNo
accountNo
list_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds pagination details, output structure, and status filter, but omits the 'account' parameter, which is present in the schema but not explained.

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?

Description is well-structured with clear headers, lists, and an example. Every sentence adds value, and it is front-loaded with purpose and usage guidelines.

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?

Given the tool's complexity (5 parameters, output schema), the description is thorough, covering most parameters and return structure. The omission of the 'account' parameter and slight overlap with schema details prevent a perfect score.

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?

Schema description coverage is 0%, so description must compensate. It explains list_id, count, offset, and status with examples and constraints. However, it fails to mention the 'account' parameter, leaving a gap for a significant parameter.

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 'List members of a specific audience' and distinguishes from siblings like search_members and list_segment_members, providing a specific verb and resource.

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?

Explicitly states when to use ('browse members of a known audience') and provides alternatives for finding specific members or segment members.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/damientilman/mailchimp-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server