Skip to main content
Glama
damientilman

Mailchimp MCP

tag_member

Add or remove tags from a single Mailchimp member without altering profile data or subscription status. Tags are created automatically if new; missing tags are ignored.

Instructions

Add or remove tags from a single member. Does not modify profile data or subscription status.

Tags are case-insensitive free-form labels. Added tags are created automatically if new; removed tags are silently ignored if not present. Idempotent. Choose the right member tool: tag_member for per-member tag changes, add_members_to_segment for bulk-adding members to a tag/segment, add_member with tags param for tagging at signup, update_member for profile/status changes, get_member_tags to check current tags.

Authenticated via API key (read scope required). Max 10 concurrent requests. Respects read-only and dry-run modes. Returns 404 error if the member does not exist.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the member. Must exist in the audience. tags_to_add: Comma-separated tag names to add (e.g. 'VIP,Returning Customer'). tags_to_remove: Comma-separated tag names to remove (e.g. 'Trial').

Returns: JSON with status ("updated"), email_address, tags array with name and status 'active'/'inactive'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
email_addressYes
tags_to_addNo
tags_to_removeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses key behaviors: no modification of profile or subscription, case-insensitive tags, idempotent, automatic creation of new tags, silent removal of missing tags, 404 for non-existent members, read-only/dry-run support, max 10 concurrent requests, and API key scope requirements.

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 sections and examples, but slightly verbose; could be tightened without losing clarity.

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 aspects: purpose, parameters, behavior, error handling, usage guidance, and return format, making it fully complete for an agent.

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?

With 0% schema description coverage, the description fully explains each parameter: list_id (format, example, source), email_address (must exist), tags_to_add/tags_to_remove (comma-separated, behavior).

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 states the tool adds or removes tags from a single member, and explicitly distinguishes from sibling tools like add_members_to_segment, update_member, and get_member_tags.

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 on when to use tag_member vs. alternatives, including add_members_to_segment for bulk, add_member for signup, update_member for profile changes, and get_member_tags to check tags.

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