Skip to main content
Glama

list_audiences

Retrieve all mailing lists with subscriber counts and statistics to manage audience data and track growth.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The list_audiences tool handler retrieves mailing lists from Mailchimp and formats the output.
    async def list_audiences(count: int = 20, offset: int = 0) -> str:
        """List all audiences (mailing lists) with subscriber counts and stats."""
        mc = get_client()
        data = await mc.get("/lists", params={"count": min(count, 100), "offset": offset})
        audiences = []
        for a in data.get("lists", []):
            stats = a.get("stats", {})
            audiences.append({
                "id": a["id"],
                "name": a.get("name", ""),
                "member_count": stats.get("member_count", 0),
                "unsubscribe_count": stats.get("unsubscribe_count", 0),
                "open_rate": stats.get("open_rate", 0),
                "click_rate": stats.get("click_rate", 0),
                "created_at": a.get("date_created", ""),
            })
        return _fmt({"total_items": data.get("total_items", 0), "audiences": audiences})
  • Registration of the list_audiences tool using the @mcp.tool() decorator.
    @mcp.tool()
Behavior2/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 implies a read-only operation by using 'List', but doesn't disclose behavioral traits such as pagination (implied by count/offset parameters), rate limits, authentication needs, or what 'stats' includes. This is inadequate for a tool with parameters and output.

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 with zero waste. It's front-loaded with the core purpose and includes additional detail ('subscriber counts and stats') that adds value without verbosity.

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 tool has parameters and an output schema, the description is minimally adequate. It states the purpose but lacks details on usage, behavior, and parameters. With annotations absent and schema coverage low, it should do more to be complete, but the output schema mitigates some gaps.

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 description must compensate. It doesn't mention parameters at all, failing to explain 'count' and 'offset' for pagination. However, with only 2 parameters and an output schema present, the baseline is 3, as the description adds no value beyond the schema.

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 'audiences (mailing lists)', specifying what the tool does. It adds detail about including 'subscriber counts and stats', which distinguishes it from a basic list. However, it doesn't explicitly differentiate from sibling tools like 'list_members' or 'list_segments', keeping it from a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context for usage, or compare to siblings like 'get_audience' or 'list_members', leaving the agent to infer usage from the name alone.

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