Skip to main content
Glama
damientilman

Mailchimp MCP

get_member_journey_events

Read-only

Filter a member's activity feed to show only automation and journey email events, answering which automation or journey emails they have 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).

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
countNo
accountNo
list_idYes
email_addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate read-only. Description adds valuable context: scanning behavior based on count parameter, side-channel mechanism for journey emails, and returned structure. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (purpose, note, args, returns). Front-loaded. The note is slightly lengthy but provides necessary context. Overall efficient.

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

Completeness4/5

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

Given the existence of an output schema, the description doesn't need to detail returns, but it does so helpfully. It covers parameters (except account), behavior, and results. For a read tool with good annotations, it is sufficiently complete.

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 coverage is 0%, so description must compensate. Description explains list_id, email_address, and count well. However, the 'account' parameter (present in schema) is not mentioned in Args, leaving a gap.

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?

Description clearly states it retrieves activity events filtered to automation/journey-related actions. This distinguishes it from siblings like get_member_activity and get_member_events. The verb and resource are specific.

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 says when to use: to answer what automation/journey emails a contact received without scanning full activity. Notes limitation about Mailchimp's API and suggests trigger_customer_journey as an alternative for enrollment.

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