Skip to main content
Glama
damientilman

Mailchimp MCP

delete_campaign

Permanently delete draft or scheduled campaigns from Mailchimp. Removes unwanted campaigns before they are sent.

Instructions

Permanently delete a campaign from the account.

Use to remove unwanted draft or scheduled campaigns. Only works on campaigns that have not been sent (status 'save' or 'schedule'). Sent campaigns cannot be deleted and will return an error. Use replicate_campaign to clone before deleting if you want to preserve settings.

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: campaign_id: The campaign ID to delete (e.g. 'abc123def4'). Must not be a sent campaign.

Returns: JSON with fields: status ("deleted"), campaign_id. Returns error if the campaign has already been sent.

Example: delete_campaign(campaign_id="abc123") -> {"status": "deleted", "campaign_id": "abc123"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully compensates: discloses irreversibility, authentication via API key, rate limits, read-only/dry-run respect, and error conditions.

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?

Well-structured with clear sections (title, paragraphs, Args, Returns, Example). No unnecessary text, every 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?

Given the simple parameter set and presence of output schema, the description is complete: covers return format, error handling, example, and all relevant behavioral notes.

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?

Only one parameter with 0% schema description coverage, but the description adds full meaning: campaign ID, example format, and constraint that it must not be a sent campaign.

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 'Permanently delete a campaign' with a specific verb and resource. It differentiates from sibling tools like replicate_campaign and other delete tools by specifying it only works on draft/scheduled campaigns.

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 states when to use ('remove unwanted draft or scheduled campaigns') and when not to ('Sent campaigns cannot be deleted'). Provides alternative (replicate_campaign) and status conditions.

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