Skip to main content
Glama
damientilman

Mailchimp MCP

update_member

Update a subscriber's status and profile fields in a Mailchimp audience. Only provided fields are changed; omitted fields remain unchanged.

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?

With no annotations, the description fully covers side effects (re-confirmation email on status change), authentication, rate limits (max 10 concurrent requests), support for read-only/dry-run modes, and specific HTTP error codes (404, 400).

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?

Well-structured with clear sections. Every sentence serves a purpose, from core definition to parameter details. No redundancy or filler.

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?

For a tool with 5 parameters, no annotations, and an output schema, the description covers all necessary context: behavior, errors, parameter details, and return fields. Nothing essential omitted.

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?

Despite 0% schema description coverage, the description adds detailed semantics for each parameter: list_id format and source, email_address requirement, status valid values, and merge field context for first_name/last_name.

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?

Explicitly states 'Update a member's profile fields or subscription status' and distinguishes from sibling tools (tag_member, unsubscribe_member, etc.) by naming each alternative's purpose.

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 a dedicated paragraph 'Choose the right member tool' that lists when to use this tool versus each sibling. Also explains that omitted fields remain unchanged and operation is idempotent.

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