Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_promo_rule

DestructiveIdempotent

Permanently delete a promo rule and all its associated promo codes. This action is irreversible.

Instructions

Permanently delete a promo rule and all its associated promo codes. Irreversible.

Side effect: every promo code attached to this rule is also deleted and stops working at checkout. Use update_promo_rule with enabled=false to disable a rule without deleting its codes.

Returns 404 if store_id or promo_rule_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID to delete.

Returns: JSON with status ('deleted'), store_id, promo_rule_id on success.

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

Input Schema

NameRequiredDescriptionDefault
accountNo
store_idYes
promo_rule_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. Addedv0.5.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations indicate destructive and idempotent; description adds irreversible deletion, cascading effect on promo codes, and specific error handling. No 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?

The description is front-loaded with key actions, clearly structured with Args/Returns, and concise without 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?

Given the presence of an output schema, the description adequately covers the return value and error cases. For a delete tool, it is complete and informative.

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 `store_id` and `promo_rule_id` but omits the optional `account` parameter. With 0% schema coverage, more detailed parameter documentation would be beneficial.

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 specifies the tool deletes a promo rule and all associated promo codes permanently. It distinguishes from `update_promo_rule` by offering an alternative for disabling without deletion.

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?

Explicitly states when to use this tool vs. `update_promo_rule` (enabled=false to disable). Also mentions irreversible nature and 404 error for invalid IDs, guiding the agent on expected behavior.

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