Mailchimp MCP Server

mailchimp_ecommerce_carts_delete

Delete a specific ecommerce cart from a Mailchimp store by providing store ID and cart ID. Removes unwanted cart data to keep your audience records clean.

Instructions

Delete a cart

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": {
      "store_id": "<store_id>",
      "cart_id": "<cart_id>"
    },
    "name": "mailchimp_ecommerce_carts_delete"
  }
}

Input Schema

Name	Required	Description	Default
`cart_id`	Yes	Cart ID to delete
`store_id`	Yes	Store ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of disclosure. It only states the action 'delete' without mentioning that deletion is permanent, whether special permissions are needed, or what happens to associated data. The verb itself implies destructive behavior, but the description adds no risk-related context.

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?

The description is a single sentence of only three words, which is extremely concise and front-loaded. It contains no filler and clearly states the core function. It works well for such a simple operation, though it could be slightly more informative.

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?

For a simple delete operation with two well-described parameters, the description is minimally viable. However, given the lack of annotations and output schema, it would benefit from noting the destructive nature or expected outcome (e.g., successful deletion). It is adequate but not thorough.

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 input schema already provides clear descriptions for both parameters (store_id, cart_id) with 100% coverage. The description adds no additional meaning beyond what the schema offers, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Delete' and the resource 'a cart', making the action unambiguous. It does not explicitly mention 'ecommerce' but the tool name disambiguates it from other delete tools. The lack of extra context on which cart or under what conditions prevents a perfect score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool, what prerequisites exist, or how it differs from other delete tools. There are no mentions of alternatives, exclusions, or when not to use it. This is a complete absence of usage guidance.

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

Deploy Server