Mailchimp MCP Server

delete_member_permanent

Permanently remove a subscriber from a Mailchimp list using their email address and list ID. This action is irreversible and prevents re-importing the contact.

Instructions

Permanently delete a subscriber. Cannot be undone — the contact cannot be re-imported.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>",
      "email": "<email>"
    },
    "name": "delete_member_permanent"
  }
}

Input Schema

Name	Required	Description	Default
`list_id`	Yes
`email`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.0May 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does well by warning that the action cannot be undone and the contact cannot be re-imported. However, it does not mention other side effects or permissions.

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?

The description is extremely concise with two sentences, front-loaded with the critical action and irreversibility warning. No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

While the description covers the irreversibility, it lacks context about prerequisites (e.g., whether the member needs to be archived first), return values, and error scenarios. An output schema exists but is not described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has two parameters with no descriptions and 0% schema description coverage. The description does not explain what list_id and email represent or how to obtain them, so it adds no value beyond the field names.

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 action (permanently delete a subscriber) and the resource (a subscriber), distinguishing it from sibling tools like archive_member or add_or_update_member.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies that this is for permanent removal with the warning about irreversibility, but does not explicitly state when to use this vs alternative actions like archiving, or what prerequisites are needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server