Skip to main content
Glama
damientilman

Mailchimp MCP

upsert_member

Idempotent

Add a new member to a Mailchimp audience or update an existing member's information in one call. No need to check for existence first.

Instructions

Add a member to an audience or update them if they already exist (idempotent upsert).

Use to reliably add-or-update a member in a single call without checking for existence first. Use add_member to strictly create a new member, or update_member to only modify an existing one.

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. status_if_new: Status to apply only when the member is newly created (default 'subscribed'). Valid: 'subscribed', 'unsubscribed', 'cleaned', 'pending', 'transactional'. merge_fields: Optional dict of merge field values (e.g. {'FNAME': 'Ada', 'LNAME': 'Lovelace'}). tags: Optional list of tag names to apply to the member.

Returns: JSON with id, email_address, status, merge_fields, tags, list_id, and timestamps. Returns an error object if the input is rejected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
accountNo
list_idYes
merge_fieldsNo
email_addressYes
status_if_newNosubscribed

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses idempotent nature, that status_if_new only applies on creation, automatic hash derivation, and return value structure. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-organized with purpose, usage, parameter list, and return info. Every sentence adds value, no redundancy.

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 functionality, parameter details, idempotency, and return value. Sufficient for an AI agent to select and invoke correctly given sibling tools and output schema.

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?

Provides detailed descriptions for all 6 parameters including format, defaults, valid values, and examples, compensating 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?

The description clearly states it adds or updates a member (idempotent upsert), and distinguishes from siblings add_member and update_member by name.

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 to use for add-or-update in one call without checking existence, and directs to siblings for strict create or update.

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