Skip to main content
Glama
damientilman

Mailchimp MCP

add_member_note

Add a CRM-style internal note to a Mailchimp audience member. Useful for sales or support context; the note is not sent to the contact.

Instructions

Add a CRM-style internal note to a member. Not sent to the contact.

Useful for sales/support context, e.g. "Asked for discount on annual plan", "Out of office until June 1st". Use update_member_note to edit an existing note instead of adding another.

Returns 404 if the member does not exist; returns 400 if note text exceeds 1000 chars.

Args: list_id: Audience/list ID. Obtain from list_audiences. email_address: Email of the member to attach the note to. Must exist in the audience. note: Note text (max 1000 chars). Plain text; markdown is not rendered in the Mailchimp UI.

Returns: JSON with id (use as note_id), email_address, note, created_at, created_by.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
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 are all false (no readOnly, idempotent, destructive), but description adds important behavioral context: note is internal, not sent to contact, max 1000 chars, and error responses. No contradictions 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?

Description is concise and well-structured: purpose first, then usage guidance, error conditions, and Args listing. It is front-loaded with key information. Slightly verbose with example notes but still efficient.

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

Completeness3/5

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

Covers purpose, usage, error conditions, and return fields (implied output schema exists). Missing explanation of the optional 'account' parameter and any authentication/permission requirements. Sufficient but not thorough.

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 description coverage is 0%, so description must explain parameters. It explains list_id, email_address, and note with context (source for list_id, existence constraint, note length and format). However, the optional 'account' parameter is completely omitted, leaving one parameter undocumented.

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 clearly states the tool adds a CRM-style internal note to a member and emphasizes it is not sent to the contact. It differentiates from sibling tools like update_member_note by explicitly saying to use that for editing.

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 guidance: useful for sales/support context with examples, and when to use update_member_note instead. Also mentions error conditions (404, 400) which helps the agent decide when to call this tool.

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