Skip to main content
Glama
damientilman

Mailchimp MCP

delete_interest_category

Remove an entire interest category and all its options from a Mailchimp audience. All subscriber associations with those interests are deleted, but subscribers remain unaffected.

Instructions

Delete an interest category and all its interest options at once.

Removes the entire category with all its options. All subscriber associations with interests in this category are removed. Subscribers themselves are not affected. Use delete_interest instead to remove a single option while keeping the category. Use list_interest_categories to find category IDs.

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. category_id: The interest category ID to delete. Obtain from list_interest_categories.

Returns: JSON with fields: status ("deleted"), category_id. Returns error if category does not exist.

Example: delete_interest_category(list_id="abc123", category_id="cat456") -> {"status": "deleted", "category_id": "cat456"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
category_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses irreversible operation, subscriber associations removal, dry-run/read-only respect, authentication, and rate limits. Fully describes behavioral traits.

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 sections (summary, args, returns, example) but slightly verbose. Each sentence adds value.

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 necessary aspects: purpose, side effects, parameter sourcing, return format, and error condition. Adequate for a delete tool with 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?

Despite 0% schema coverage, description adds explicit meaning: source of IDs, example values, and usage context for both parameters.

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?

States verb 'delete' and resource 'interest category and all its interest options' with explicit contrast to sibling 'delete_interest' for single option removal.

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

Usage Guidelines4/5

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

Provides alternative tool (delete_interest) and context for obtaining IDs. Lacks explicit 'when not to use' but gives clear guidance via alternatives.

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