Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

cancel_send

Stop a currently sending Mailchimp campaign, preventing further deliveries to unsent recipients. Irreversible action for campaigns in 'sending' status.

Instructions

Cancel a campaign mid-send, stopping delivery to remaining recipients.

Only works on campaigns with status 'sending'. Already-delivered emails cannot be recalled. Irreversible. Use unschedule_campaign for scheduled (not yet sending) campaigns instead.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be in 'sending' status.

Returns: JSON with status ("cancelled"), campaign_id. Error if not currently sending.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "cancel_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
campaign_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses that the action is irreversible, cannot recall delivered emails, and only succeeds if the campaign is currently sending. Annotations are all false, but the description adds essential behavioral context beyond them without contradiction.

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?

Concise and well-structured: a brief statement followed by bullet points for conditions, arguments, and return value. No unnecessary words.

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?

Despite output schema not displayed, the description mentions the return JSON structure. It covers constraints, prerequisites, and error conditions adequately for a cancellation tool.

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?

The description explains 'campaign_id' format and requirement, but does not cover the optional 'account' parameter. With 0% schema description coverage, the description partially compensates but leaves a gap.

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 explicitly states the tool cancels a campaign mid-send, using a specific verb ('Cancel') and resource ('campaign'). It distinguishes from sibling 'unschedule_campaign' by noting it's for scheduled campaigns, not sending ones.

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?

Clear guidelines: only works on campaigns with status 'sending', and advises using 'unschedule_campaign' for scheduled campaigns. Explicitly states when to use and when not.

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