Skip to main content
Glama

delete_campaign

Permanently delete an unsent Mailchimp campaign to manage your campaign list. Provide the campaign ID for the deletion.

Instructions

Permanently delete a campaign. Only works on campaigns that haven't been sent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The delete_campaign tool handler — an async MCP tool that permanently deletes a Mailchimp campaign by calling DELETE /campaigns/{campaign_id} on the Mailchimp API.
    @mcp.tool()
    async def delete_campaign(campaign_id: str) -> str:
        """Permanently delete a campaign. Only works on campaigns that haven't been sent."""
        mc = get_client()
        await mc.delete(f"/campaigns/{campaign_id}")
        return _fmt({"campaign_id": campaign_id, "message": "Campaign deleted permanently."})
  • The tool is registered via the @mcp.tool() decorator on line 860, making it available as an MCP tool.
    @mcp.tool()
    async def delete_campaign(campaign_id: str) -> str:
        """Permanently delete a campaign. Only works on campaigns that haven't been sent."""
        mc = get_client()
        await mc.delete(f"/campaigns/{campaign_id}")
        return _fmt({"campaign_id": campaign_id, "message": "Campaign deleted permanently."})
Behavior4/5

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

Discloses that deletion is permanent and only applicable to unsent campaigns, which is sufficient for basic behavioral transparency. However, with no annotations, it could additionally note irreversibility or authentication requirements.

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?

Extremely concise with two sentences: first states the action, second adds a crucial condition. No filler, and the key information is front-loaded.

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

Completeness4/5

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

For a simple 1-parameter tool with an output schema, the description covers the essential behavior and constraint. It could be improved by mentioning the output or irreversibility, but overall it is mostly complete.

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

Parameters1/5

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

Schema coverage is 0%, and the description provides no explanation for the required parameter 'campaign_id', such as its format, source, or how to obtain it. The description fails to add meaning beyond the 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 deletes a campaign permanently and specifies the condition that it only works on unsent campaigns, distinguishing it from other campaign-related tools like cancel_campaign.

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 clear context by stating the prerequisite that the campaign must not have been sent, implying when to use (unsent campaigns) but does not explicitly mention alternatives or when not to use.

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/AlexlaGuardia/mcp-mailchimp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server