Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_ecommerce_carts_add

Create a new cart in Mailchimp to track abandoned carts and recover lost sales.

Instructions

Add a new cart (for abandoned cart tracking)

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>",
      "id": "<id>",
      "customer": "<customer>",
      "currency_code": "<currency_code>",
      "order_total": "<order_total>",
      "lines": "<lines>"
    },
    "name": "mailchimp_ecommerce_carts_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique cart ID
linesYesCart line items
customerYesCustomer information
store_idYesStore ID
order_totalYesCart total
checkout_urlNoCart checkout URL
currency_codeYesISO 4217 currency code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only says 'Add a new cart' and mentions abandoned cart tracking, but does not disclose side effects, duplicate ID behavior, required permissions, or response format. As a mutation tool, more transparency is needed.

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, front-loaded sentence: 'Add a new cart (for abandoned cart tracking)'. Every word earns its place, with no filler or repetition of schema information. It is appropriately sized for a simple create operation.

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?

With no output schema and no annotations, the description is somewhat sparse. It captures the primary purpose and the schema fully documents the inputs, but it omits prerequisites (e.g., store must exist), return behavior, and error conditions. The clear purpose and complete schema keep it from being severely incomplete.

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 schema covers 100% of the 7 parameters with descriptions, so the baseline is 3. The description adds no extra parameter-specific details; the 'abandoned cart tracking' context hints at why fields like order_total and checkout_url are relevant, but the schema already documents them fully.

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 states 'Add a new cart' with a clear verb and resource, and the parenthetical 'for abandoned cart tracking' specifies the domain. This distinguishes it from sibling tools like carts_update, carts_delete, or orders_add, which serve different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for abandoned cart tracking' provides clear context on when to use this tool. It implies usage for creating carts to track abandoned checkouts, and the operation is distinct from update/delete/list siblings. However, it does not explicitly mention exclusions or alternative tools when not to use it.

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