Skip to main content
Glama

list_members

Retrieve audience members from Mailchimp lists with filtering options for subscription status, count, and offset to manage subscriber data.

Instructions

List members of an audience. Filter by status: subscribed, unsubscribed, cleaned, pending, transactional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
statusNo
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `list_members` tool implementation, registered with `@mcp.tool()` and using the Mailchimp API client to fetch list members.
    @mcp.tool()
    async def list_members(
        list_id: str,
        status: str = "",
        count: int = 20,
        offset: int = 0,
    ) -> str:
        """List members of an audience. Filter by status: subscribed, unsubscribed, cleaned, pending, transactional."""
        mc = get_client()
        params: dict[str, Any] = {"count": min(count, 100), "offset": offset}
        if status:
            params["status"] = status
        data = await mc.get(f"/lists/{list_id}/members", params=params)
        members = []
        for m in data.get("members", []):
            members.append({
                "email": m.get("email_address", ""),
                "status": m.get("status", ""),
                "full_name": m.get("full_name", ""),
                "tags_count": m.get("tags_count", 0),
                "rating": m.get("member_rating", 0),
                "last_changed": m.get("last_changed", ""),
                "id": m.get("id", ""),
            })
        return _fmt({"total_items": data.get("total_items", 0), "members": members})
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions filtering by status but doesn't describe pagination behavior (implied by count/offset parameters), rate limits, authentication requirements, or what happens when list_id doesn't exist. For a read operation with 4 parameters, this is insufficient.

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, efficient sentence that states the core functionality upfront. Every word contributes to understanding what the tool does without any wasted text.

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 that there's an output schema (which handles return values), the description's main gaps are behavioral context and parameter explanations. For a list operation with pagination and filtering, the description should ideally mention pagination behavior and differentiate from similar tools, but the presence of an output schema reduces the completeness burden.

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 the schema provides no parameter descriptions. The description mentions 'Filter by status' which explains the purpose of the 'status' parameter and lists possible values, but doesn't explain 'list_id', 'count', or 'offset'. It adds some value but doesn't fully compensate for the schema's lack of descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('List') and resource ('members of an audience'), and specifies filtering by status. However, it doesn't explicitly differentiate from sibling tools like 'search_members' or 'get_segment_members', which appear to have overlapping functionality.

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 about when to use this tool versus alternatives like 'search_members' or 'get_segment_members'. The description only states what the tool does, not when it's appropriate compared to other listing/searching tools in the sibling set.

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/AlexlaGuardia/mcp-mailchimp'

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