Skip to main content
Glama
damientilman

Mailchimp MCP

update_member_note

Replace an existing member note's text entirely. Specify the list ID, member email, note ID, and the new note content.

Instructions

Update the text of an existing member note. Replaces the entire note body.

Use list_member_notes to find note_ids. Use add_member_note instead to create a new note rather than overwriting; use delete_member_note to remove a note.

Returns 404 if the note or member does not exist.

Args: list_id: Audience/list ID. Obtain from list_audiences. email_address: Email of the member who owns the note. note_id: Note ID to update. Obtain from list_member_notes. note: New note text (max 1000 chars). Replaces the previous text entirely.

Returns: JSON with id, email_address, note (new value), updated_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
accountNo
list_idYes
note_idYes
email_addressYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Description discloses that it replaces the entire note body, returns 404 if note/member doesn't exist, and returns JSON with fields. Annotations are neutral. Missing details on idempotency or concurrency, but overall good.

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 and well-structured: purpose, usage guidance, args, returns. No redundant information.

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 the output schema is described, annotations are basic, description covers prerequisites, behavior, error handling, and return format. Fully complete for the 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?

Description explains all required parameters (list_id, email_address, note_id, note) with sources and max length. However, it omits the optional 'account' parameter from the schema, which lacks description coverage.

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 it updates the text of an existing member note, replacing the entire note body. It differentiates from sibling tools like add_member_note (create) and delete_member_note (remove).

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 tells when to use this tool vs alternatives: use add_member_note to create, delete_member_note to remove, and list_member_notes to find note_ids. Also provides prerequisites for obtaining IDs.

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