Mailchimp MCP Server

mailchimp_ecommerce_promo_codes_list

List all promo codes for a given promo rule in Mailchimp ecommerce. Specify store ID and rule ID to retrieve codes.

Instructions

Get all promo codes for 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>"
    },
    "name": "mailchimp_ecommerce_promo_codes_list"
  }
}

Input Schema

Name	Required	Description
`count`	No	Number of records to return
`offset`	No	Number of records to skip
`rule_id`	Yes	Promo rule ID
`store_id`	Yes	Store ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3/5.0

Behavior1/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 of behavioral disclosure. It merely restates the tool name without revealing return format, pagination behavior, filtering constraints, or the read-only nature of the operation. The description adds no meaningful behavioral context beyond what the name and schema already imply.

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 words. It is front-loaded with the action and resource, making it immediately clear what the tool does.

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?

There is no output schema, so the description should explain what is returned. It does not mention pagination (count/offset) or any filtering behavior. It also lacks guidance on when to use this tool relative to sibling e-commerce tools, leaving the agent with incomplete context for invocation.

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 descriptions cover 100% of parameters, so the baseline is 3. The description does not add any semantic value beyond what the schema already provides; the phrase 'for a promo rule' aligns with rule_id but is already documented as 'Promo rule ID'.

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 states the action (get all) and resource (promo codes) scoped to a specific promo rule. It is distinctly different from sibling tools like mailchimp_ecommerce_promo_codes_add (which adds) and mailchimp_ecommerce_promo_rules_list (which lists rules, not codes).

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?

There is no guidance on when to use this tool versus alternatives such as promo_codes_add or promo_rules_list. No context is provided about the relationship between store_id and rule_id or when pagination parameters are appropriate.

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

Deploy Server