Skip to main content
Glama
damientilman

Mailchimp MCP

create_store_cart

Create a new cart for an e-commerce store with line items and customer reference. Enables abandoned-cart recovery workflows by pushing cart data from external systems into Mailchimp.

Instructions

Create a cart in a store with line items and a customer reference. Used to push abandoned-cart data from an external system into Mailchimp for recovery workflows.

cart_id is client-supplied (Mailchimp does not auto-generate it). The customer must already exist in the store; create them via Mailchimp's customer endpoints first if not. Use update_store_cart to modify after creation.

Args: store_id: E-commerce store ID. cart_id: Client-supplied unique ID for the new cart (e.g. 'cart_42'). customer_id: ID of an existing customer in the store. currency_code: ISO 4217 currency code (e.g. 'USD', 'EUR'). order_total: Total order amount (line items + tax + shipping if any). lines_json: JSON string with the cart line items array. Example: '[{"id": "line_1", "product_id": "p_1", "product_variant_id": "p_1_red", "quantity": 2, "price": 19.99}]' checkout_url: Optional URL to resume the cart (used in recovery emails). tax_total: Optional tax portion of order_total.

Returns: JSON with id, customer, currency_code, order_total, checkout_url, created_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
cart_idYes
store_idYes
tax_totalNo
lines_jsonYes
customer_idYes
order_totalYes
checkout_urlNo
currency_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare it's not read-only, not idempotent, not destructive. Description adds key behavioral details: cart_id is client-supplied (no auto-generation), customer must exist before creation. This goes beyond annotations without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured: brief intro, then list of args with descriptions, plus return info. Front-loaded with purpose. Example for lines_json is helpful but slightly lengthy; overall efficient for the complexity.

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?

Covers purpose, usage, all parameters, return value, and preconditions. Output schema exists but description still provides useful return field list. Complete for a tool with 9 parameters and external dependencies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but description explains all 9 parameters in detail, including examples for lines_json and clarifying currency_code, checkout_url, etc. Adds significant meaning beyond the schema titles and types.

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?

Clearly states 'Create a cart in a store with line items and a customer reference.' and specifies the use case 'push abandoned-cart data from an external system into Mailchimp for recovery workflows.' This distinguishes it from sibling tools like create_store_order and update_store_cart.

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 (abandoned-cart recovery), preconditions (customer must already exist via create_store_customer), and alternative (use update_store_cart for modifications). Provides clear context and exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/damientilman/mailchimp-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server