Skip to main content
Glama
damientilman

Mailchimp MCP

get_member_journey_events

Filter a Mailchimp member's activity to show only automation and journey email events, answering which automated or journey emails they received.

Instructions

Retrieve a member's activity events filtered to automation- and journey-related actions.

Returns the subset of the member's activity feed that relates to Classic Automations and (where Mailchimp surfaces them) Customer Journey emails. Useful to answer "what automation or journey emails has this contact received?" without scanning their full activity.

Note: Mailchimp does not expose a public read API for Customer Journeys themselves. Journey emails do appear in the activity feed as automation-typed actions, so this tool surfaces them via that side-channel rather than reading the journey graph directly. Use trigger_customer_journey to enroll a contact into a specific journey step (the only journey write available via API).

Authenticated via API key. Max 10 concurrent requests. Read-only, safe to retry.

Args: list_id: Audience/list ID (10-char alphanumeric). Obtain from list_audiences. email_address: Email of the member. Must exist in the audience. count: Number of activity rows to scan before filtering (1-1000, default 50). Raise if the member is highly active and you suspect automation events are missed.

Returns: JSON with email_address, scanned (raw row count looked at), total_journey_events (after filtering), and events array. Each event: action (raw action type), timestamp, title (campaign / automation title if present), url (link clicked if any), campaign_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
email_addressYes
countNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses read-only safe nature, max 10 concurrent requests, authentication via API key, and the side-channel behavior for journey events. Since no annotations are provided, the description fully carries the burden of transparency.

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 sections (main description, notes, authentication, args, returns). Every sentence adds value without redundancy, and it is front-loaded with the primary purpose.

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?

Coverage is thorough: purpose, usage guidance, behavioral notes, parameter details, and output schema description. Despite the tool's complexity, no gaps remain.

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 compensates by detailing each parameter: list_id format and source, email_address requirement, count's purpose, default, and recommendation for highly active members. Also describes the output structure.

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?

Explicitly states 'Retrieve a member's activity events filtered to automation- and journey-related actions.' Uses specific verb-retrieve and resource-events, and clearly distinguishes from sibling tools like get_member_activity by mentioning filtering.

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?

Provides explicit context: 'Useful to answer what automation or journey emails has this contact received?' and includes when-not-to-use by noting Mailchimp's lack of public Journey API, along with an alternative tool (trigger_customer_journey) for write operations.

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