Mailchimp MCP Server

mailchimp_ecommerce_promo_codes_add

Add a promo code to an existing ecommerce promo rule in Mailchimp. Specify store, rule, code details, and optional redemption URL to enable customer discounts.

Instructions

Add a promo code to a promo rule

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>",
      "rule_id": "<rule_id>",
      "id": "<id>",
      "code": "<code>"
    },
    "name": "mailchimp_ecommerce_promo_codes_add"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Promo code ID
`code`	Yes	Promo code text
`enabled`	No	Whether code is enabled
`rule_id`	Yes	Promo rule ID
`store_id`	Yes	Store ID
`redemption_url`	No	Promo code redemption URL

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?

No annotations are provided, so the description carries the full burden. It only says 'add', which implies creation, but does not disclose whether the operation is idempotent, whether existing codes are overwritten, what happens on duplicate IDs, or what the response contains. Minimal behavioral disclosure.

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, direct sentence with no unnecessary wording. It is front-loaded with the action and resource, making it easy to parse quickly.

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?

For a write operation with no annotations and no output schema, the description is too sparse. It does not explain the necessity of an existing promo rule, potential uniqueness constraints on the code ID, or return behavior. Sibling tools for adding other ecommerce entities suggest more context could be provided.

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?

Schema coverage is 100%, so the schema already fully describes all six parameters. The description adds no additional semantic value beyond the schema, such as relationships between parameters or format requirements, so the baseline of 3 applies.

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 'Add a promo code to a promo rule' clearly states the action (add) and the resource (promo code) within the context of a promo rule. It distinguishes from sibling tools like mailchimp_ecommerce_promo_codes_list, though it does not explicitly mention store scope.

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 on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing an existing promo rule) or when a different operation (update/delete) would be appropriate. The description only states the action without context.

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

Deploy Server