Skip to main content
Glama
damientilman

Mailchimp MCP

update_member

Update a member's profile fields and subscription status. Idempotent; omitted fields remain unchanged. Changing status to 'pending' sends a re-confirmation email.

Instructions

Update a member's profile fields or subscription status. Does not manage tags.

Only provided fields are updated; omitted fields remain unchanged. Idempotent: re-applying the same values is safe. Side effect: changing status to 'pending' triggers a re-confirmation email. Choose the right member tool: update_member for profile/status changes, tag_member for tag management, unsubscribe_member as shortcut for opt-out, add_member if the contact does not exist yet, batch_subscribe for bulk operations.

Authenticated via API key. Max 10 concurrent requests. Respects read-only and dry-run modes. Returns 404 error if member does not exist. Returns 400 if status transition is invalid (e.g. cleaned to subscribed).

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the member to update. Must exist in the audience. status: New status: 'subscribed', 'unsubscribed', 'cleaned', 'pending'. first_name: New first name (FNAME merge field). last_name: New last name (LNAME merge field).

Returns: JSON with id, email_address, status, full_name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
email_addressYes
statusNo
first_nameNo
last_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses behavior: only provided fields updated, idempotent, side effect of re-confirmation email on status='pending'. Also mentions authentication, rate limit, read-only/dry-run modes, and error responses (404, 400). No annotations provided, but description fully compensates.

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 front-loading and bullet-style args. Slightly lengthy but each sentence adds value; could be trimmed slightly but still efficient.

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?

Covers all necessary aspects: purpose, usage guide, behavior, parameter details, errors, authentication, rate limits. Output schema describes return values; description is complete for a mutation tool.

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?

Adds detailed meaning beyond schema: list_id format and example, email_address requirement, valid status values, merge field names. Compensates for 0% schema 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?

Clearly states the action (update), resource (member), and scope (profile fields or subscription status). Distinguishes from sibling tools like tag_member and unsubscribe_member.

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 guides when to use this tool vs. alternatives (tag_member, unsubscribe_member, add_member, batch_subscribe). Notes idempotency and side effects re: re-confirmation email.

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