Skip to main content
Glama
damientilman

Mailchimp MCP

list_store_carts

Read-only

List carts for a Mailchimp e-commerce store, including abandoned carts, with customer info and totals. Use to trigger recovery automations for incomplete purchases.

Instructions

List carts for a store, including abandoned ones, with customer and total info.

Carts in Mailchimp typically represent in-progress purchases synced from a connected storefront. Use for abandoned-cart workflows: filter by recent created_at, segment by cart total, then trigger a recovery automation. Use get_store_cart for a single cart with line items. Use list_store_orders for completed purchases.

Returns 404 if store_id is invalid.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. count: Number of carts to return (1-1000, default 20). offset: Pagination offset.

Returns: JSON with store_id, total_items, and carts array. Each cart: id, customer (object with id, email_address, opt_in_status), currency_code, order_total, tax_total, checkout_url, created_at, updated_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo
accountNo
store_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Description adds context beyond annotations: includes abandoned carts, returns 404 for invalid store_id. Annotations already declare readOnlyHint=true and non-destructive, so description complements well.

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?

Efficiently structured: first sentence states purpose, then context, comparisons, Args, Returns. Every sentence adds value without redundancy.

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?

Complete for a read-only list tool with 4 parameters. Provides return shape in detail, with output schema already present. Covers all necessary information.

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?

Despite 0% schema description coverage, the Args section fully documents all parameters: store_id (with source from list_ecommerce_stores), count (default and range), offset. This compensates completely.

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 tool's purpose: 'List carts for a store, including abandoned ones, with customer and total info.' It distinguishes from siblings like get_store_cart and list_store_orders by specifying scope and use case.

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?

Explicit guidance provided: 'Use for abandoned-cart workflows... Use get_store_cart for a single cart with line items. Use list_store_orders for completed purchases.' Also notes error condition for invalid store_id.

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