Skip to main content
Glama
damientilman

Mailchimp MCP

add_member_event

Record a custom event for an audience member to trigger automations and power segmentation.

Instructions

Record a custom event for an audience member (e.g. 'purchased', 'viewed_pricing').

Use to log member activity that can trigger automations or power segmentation. Use get_member_events to read a member's recorded events and get_member_goals for tracked Goals.

Authenticated via API key. Max 10 concurrent requests. Respects read-only and dry-run modes.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: The member's email address. The subscriber hash is derived automatically. name: Event name (letters, numbers, underscores; max 30 chars, e.g. 'purchased'). properties: Optional dict of custom key/value properties describing the event. account: Optional account name (e.g. 'marketing') configured via MAILCHIMP_API_KEY_. Omit to use the default account. See list_accounts.

Returns: JSON confirming the event was recorded, or an error object if the member is not found or the input is rejected. On success the Mailchimp API returns an empty body (HTTP 204).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
accountNo
list_idYes
propertiesNo
email_addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Adds details beyond annotations: authentication via API key, max 10 concurrent requests, respects read-only/dry-run modes, and describes return format (JSON confirmation or error, HTTP 204 on success). No contradictions.

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?

Structured with purpose, guidelines, then Args section. Front-loaded with key info. Slightly long but each sentence adds value. Could be tightened but acceptable.

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 5 parameters, 0% schema coverage, and output schema present, description covers all aspects: purpose, usage, alternatives, auth, rate limits, parameter details, return format. Very complete.

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 coverage, description provides thorough parameter details: list_id format and source, email address derivation, name constraints and examples, properties as optional dict, account configuration. Adds significant meaning beyond schema types.

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 'Record a custom event for an audience member' with examples. Distinguishes from siblings by noting get_member_events for reading and get_member_goals for goals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use: 'log member activity that can trigger automations or power segmentation.' Mentions alternatives for reading. Includes authentication, rate limits, and dry-run modes, but does not explicitly state when not to use.

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