Mailchimp MCP Server

mailchimp_ecommerce_stores_delete

Delete a Mailchimp ecommerce store by providing its store ID. Removes the store and associated data from your Mailchimp account.

Instructions

Delete a store

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>"
    },
    "name": "mailchimp_ecommerce_stores_delete"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.2/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 behavioral disclosure. It states only that a store is deleted, but does not reveal irreversible consequences, potential cascading effects on related resources (e.g., products, orders), permission requirements, or what the response indicates. This is a significant gap for a destructive operation.

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?

The description is extremely concise, consisting of a single four-word sentence. Every word contributes to the meaning, and it is appropriately sized for a simple delete operation. There is no wasted text or redundant information.

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

Completeness2/5

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

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is minimally complete in that it identifies the action. However, it lacks essential context about deletion side effects, irreversibility, or success/failure semantics. For a destructive operation, this incompleteness is a notable flaw.

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 a 100% description coverage for the single parameter `store_id` ('Store ID to delete'). The tool description adds no additional parameter meaning beyond what the schema states, so the baseline score of 3 applies.

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 'Delete a store' uses a specific verb and resource, clearly distinguishing the action from other store operations like add, update, or list. It is concise and unambiguous, matching or exceeding the clarity of the high-scoring example 'List ALL calls in date range'.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, consequences, or situations where deletion is appropriate or inappropriate, nor any reference to sibling tools or alternative approaches.

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

Deploy Server