Skip to main content
Glama
damientilman

Mailchimp MCP

get_campaign_recipients

Retrieve delivery status and open count for each recipient of a sent Mailchimp campaign. Verify who received and who opened.

Instructions

Retrieve the delivery roster for a sent campaign showing each recipient's delivery status and open count.

Use to verify who received a campaign and whether they opened it. Use get_email_activity for detailed per-recipient timelines (clicks, bounces with timestamps). Use get_campaign_report for aggregate metrics. Only works for sent campaigns; returns error for drafts or scheduled.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). Read-only, safe to retry.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Number of recipients to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items (int) and recipients array. Each recipient: email_address, status ('sent', 'hard', 'soft'), open_count (int), last_open (ISO 8601 or null).

Example: get_campaign_recipients(campaign_id="abc123", count=100) -> {"total_items": 5000, "recipients": [{"email_address": "jane@co.com", "status": "sent", "open_count": 3, ...}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description discloses key behavioral traits: read-only, safe to retry, requires API key, subject to Mailchimp API rate limits (max 10 concurrent requests), and error condition for non-sent campaigns. This covers safety and retry implications.

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 well-structured with a summary, usage context, behavioral notes, parameter details, return format, and example. Every sentence is informative and non-redundant, achieving high information density without verbosity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all essential aspects: purpose, usage guidance, constraints, parameter semantics, return structure, and example. Even though an output schema exists, the description provides a clear, self-contained explanation that lets the agent understand exactly what to expect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates via an 'Args' section. It explains each parameter's purpose, constraints (e.g., count range 1-1000, default 20), and provides an example for campaign_id. This adds critical meaning beyond the bare schema.

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?

The description starts with a clear verb 'Retrieve' and specifies the resource 'delivery roster for a sent campaign showing each recipient's delivery status and open count'. It distinguishes from sibling tools like get_email_activity and get_campaign_report, making the purpose unambiguous.

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 this tool ('verify who received a campaign and whether they opened it') and provides alternatives: 'Use get_email_activity for detailed per-recipient timelines... Use get_campaign_report for aggregate metrics.' Also notes the constraint 'Only works for sent campaigns; returns error for drafts or scheduled.'

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