Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_members_delete

Delete a member from a Mailchimp list using list ID and email address, unsubscribing and archiving them.

Instructions

Delete (unsubscribe and archive) a member from a list

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_address": "<email_address>"
    },
    "name": "mailchimp_members_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYesList ID
email_addressYesEmail address to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It states that 'delete' translates to 'unsubscribe and archive', which is useful behavioral context. However, it does not disclose potential side effects (e.g., triggering automation, sending notifications), permissions required, or error conditions (e.g., member not found). The description is not misleading but is incomplete for full transparency.

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 a single, compact sentence that front-loads the action ('Delete') and immediately clarifies scope in parentheses. Every word earns its place; there is no redundancy or filler.

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?

The tool is simple (2 required parameters, no output schema), and the description states the core behavior. However, it does not explain return values or error handling, which is needed since there is no output schema. The absence of details like whether the member must already exist or how success is reported leaves a gap in completeness.

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

Parameters3/5

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

Schema coverage is 100% with both parameters having descriptions ('List ID' and 'Email address to delete'). The tool description adds minimal extra meaning—'from a list' maps to list_id, and 'a member' maps to email_address—but does not enrich parameter understanding beyond the schema. Baseline of 3 is appropriate.

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 uses a specific verb 'Delete' and clarifies the operation as 'unsubscribe and archive', which precisely distinguishes it from sibling tools like mailchimp_members_archive (which only archives) and mailchimp_members_update (which updates). It clearly identifies the resource as 'a member from a list'.

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 usage by explaining the deletion semantics (unsubscribe and archive), but it does not explicitly state when to use this tool over alternatives. No mention of exclusions or conditions, such as if the member already exists or if the list is archived. The guidance is implicit rather than explicit.

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

Deploy Server

Other Tools