Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_ecommerce_products_delete

Remove a product from a Mailchimp ecommerce store using the store ID and product ID. Delete unwanted or outdated product data to keep your catalog accurate.

Instructions

Delete a product

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

Input Schema

NameRequiredDescriptionDefault
store_idYesStore ID
product_idYesProduct ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. 'Delete a product' clearly indicates a destructive operation, but it does not disclose irreversibility, side effects, or required permissions. The absence of any additional behavioral context leaves significant gaps for a mutation tool.

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 a single, concise sentence with no filler or redundant information. It is front-loaded and efficiently communicates the core purpose.

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 fully documented parameters, the description is minimally viable. However, it lacks any operational context such as whether the deletion is permanent, affects related resources, or requires specific data to have been fetched first. The completeness relies entirely on the clear schema and obvious action.

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 provides 100% coverage with clear descriptions for both parameters ('Store ID' and 'Product ID to delete'). The description adds no additional semantic value beyond what the schema already specifies, matching the baseline for high schema coverage.

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 product' uses a specific verb and resource, clearly distinguishing it from sibling product operations like list, get, add, and update. It is unambiguous and directly states the tool's function.

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, such as when deleting a product versus a cart or customer. It lacks context about prerequisites, effects, or exclusions, offering only the bare action.

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