Skip to main content
Glama

get_audience

Retrieve detailed information and statistics for a specific Mailchimp audience to analyze subscriber data and track performance metrics.

Instructions

Get detailed info and stats for a specific audience.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The 'get_audience' tool handler which fetches details and statistics for a specific Mailchimp list. It is registered with the @mcp.tool() decorator.
    @mcp.tool()
    async def get_audience(list_id: str) -> str:
        """Get detailed info and stats for a specific audience."""
        mc = get_client()
        a = await mc.get(f"/lists/{list_id}")
        stats = a.get("stats", {})
        return _fmt({
            "id": a["id"],
            "name": a.get("name", ""),
            "permission_reminder": a.get("permission_reminder", ""),
            "member_count": stats.get("member_count", 0),
            "unsubscribe_count": stats.get("unsubscribe_count", 0),
            "cleaned_count": stats.get("cleaned_count", 0),
            "campaign_count": stats.get("campaign_count", 0),
            "open_rate": stats.get("open_rate", 0),
            "click_rate": stats.get("click_rate", 0),
            "last_campaign_sent": stats.get("campaign_last_sent", ""),
            "created_at": a.get("date_created", ""),
        })
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions 'detailed info and stats,' implying a read-only operation, but fails to disclose critical behaviors like authentication needs, rate limits, error handling, or whether it returns real-time or cached data. This leaves significant gaps for an agent to invoke it correctly.

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 no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Every word contributes directly to the tool's purpose.

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's low complexity (1 parameter) and the presence of an output schema (which likely details return values), the description is minimally adequate. However, with no annotations and incomplete parameter semantics, it lacks sufficient context for safe and effective use, especially regarding behavioral aspects like data freshness or access controls.

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?

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic context. The description adds minimal value by implying the parameter identifies 'a specific audience,' but does not explain the 'list_id' format, constraints, or examples. This partially compensates but remains inadequate for full understanding.

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 'Get' and the resource 'detailed info and stats for a specific audience,' which is specific and actionable. However, it does not explicitly differentiate from sibling tools like 'list_audiences' (which likely lists multiple audiences) or 'get_member' (which focuses on individual members), leaving some ambiguity in scope.

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 lacks context such as prerequisites (e.g., needing an audience ID), exclusions (e.g., not for aggregated stats), or comparisons to siblings like 'list_audiences' for bulk retrieval or 'get_member' for member-specific data.

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