Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_member_events

Read-only

Retrieve custom API-triggered events (e.g., purchases, sign-ups) for a specific Mailchimp audience member. Use to access events sent via the Events API, distinct from email engagement data.

Instructions

Retrieve custom API-triggered events for a specific member (e.g. "purchased", "signed_up").

Use to view events sent to Mailchimp via the Events API. These are custom application events, not email interactions (opens, clicks); use get_member_activity for email engagement data. Returns empty if no custom events have been recorded for the member.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email address of the member. Must exist in the audience. count: Number of events to return (1-1000, default 20).

Returns: JSON with email_address, total_items (int), and events array. Each event: name (string, event name), occurred_at (ISO 8601), properties (object, custom key-value data or null).

Example: get_member_events(list_id="abc123", email_address="jane@co.com") -> {"email_address": "jane@co.com", "total_items": 5, "events": [{"name": "purchased", "occurred_at": "2025-06-01T10:00:00Z", "properties": {"product": "T-Shirt"}}]}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>",
      "email_address": "<email_address>"
    },
    "name": "get_member_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
accountNo
list_idYes
email_addressYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, non-destructive. Description adds that it returns empty if no events and describes return structure, complementing annotations without contradiction.

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?

Concise one-sentence purpose followed by usage guidance, parameter docs, return type, and example. Well-structured with no fluff.

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?

Given low schema coverage and availability of output schema in description, the description fully covers purpose, parameters, return structure, and usage context – comprehensive for a read-only tool.

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

Parameters4/5

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

Schema coverage is 0%, but description documents list_id, email_address, and count with context (e.g., list_id from list_audiences, email must exist, count default 20). However, account parameter is present in schema but not described in args; slight 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?

Clearly states 'Retrieve custom API-triggered events for a specific member', distinguishing from get_member_activity which is for email engagement. Specific verb and resource.

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 (custom application events) and when not (email interactions) and directs to get_member_activity as alternative. Also notes empty return if no events.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools