Skip to main content
Glama
damientilman

Mailchimp MCP

delete_member

Permanently delete a member and all associated data from an audience. Use for complete data removal, such as GDPR right-to-erasure requests.

Instructions

Permanently delete a member and all their data from an audience.

Use only for complete data removal (e.g. GDPR right-to-erasure requests). All activity history, merge field data, and tag associations are permanently lost. Use unsubscribe_member instead to stop sending while preserving data for reporting. There is no undo.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). This operation is irreversible. Respects read-only and dry-run modes.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email address of the member to permanently delete. Must exist in the audience.

Returns: JSON with fields: status ("permanently_deleted"), email_address. Returns error if the member does not exist.

Example: delete_member(list_id="abc123", email_address="jane@co.com") -> {"status": "permanently_deleted", "email_address": "jane@co.com"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
email_addressYes

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 discloses behavioral traits: permanence, data loss (activity history, merge fields, tags), authentication via API key, Mailchimp API rate limits (max 10 concurrent requests), and respect for read-only/dry-run modes. No contradictions with annotations as none exist.

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?

Description is well-structured with clear sections: purpose, usage guidance, details, Args, Returns, Example. It is not overly verbose for the amount of information conveyed, but could be slightly more concise in the details section. Still effectively front-loaded with key info.

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 tool's irreversible nature and complexity, the description covers all necessary context: purpose, when to use/alternatives, side effects, authentication, rate limits, parameter details, return format, and an example. No gaps remain.

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?

Schema has 0% description coverage (no parameter descriptions). The description compensates fully by explaining both parameters: list_id (how to obtain it, example) and email_address (must exist). Provides a concrete example with dummy values, adding substantial meaning beyond the raw schema.

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 the tool's action: 'Permanently delete a member and all their data from an audience.' It distinguishes itself from the sibling tool 'unsubscribe_member' by specifying the alternative use case. The verb 'delete' combined with the resource 'member' is specific and unambiguous.

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 provides when to use (GDPR right-to-erasure) and when not to (use unsubscribe_member for stop sending while preserving data). Also notes irreversibility and no undo, guiding the AI agent to appropriate behavior.

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