Skip to main content
Glama
damientilman

Mailchimp MCP

get_store_cart

Read-only

Retrieve a shopping cart's full details including line items, customer, and totals. Use this to inspect abandoned carts before sending recovery emails.

Instructions

Retrieve a single cart with its full line items, customer, and total breakdown.

Use to inspect what's in an abandoned cart before triggering a recovery email. Use list_store_carts to browse and discover cart_ids.

Returns 404 if store_id or cart_id is invalid.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. cart_id: Cart ID. Obtain from list_store_carts.

Returns: JSON with id, customer, currency_code, order_total, tax_total, checkout_url, lines (array of {id, product_id, product_variant_id, quantity, price}), created_at, updated_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
cart_idYes
store_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true, so description adds value by specifying 404 error behavior and detailing return structure. No contradictions; idempotency hint is not addressed but not required.

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?

Description is concise and well-structured with overview, usage guide, error handling, bulleted args, and returns. No redundant sentences, every line serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of an output schema and read-only annotations, the description covers key aspects: purpose, parameter sources, error case, and return shape. Only minor gap is the undocumented account parameter, but overall sufficient for a straightforward read operation.

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

Parameters4/5

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

Schema coverage is 0%, but description explains store_id and cart_id with sources (list_ecommerce_stores, list_store_carts). However, the optional 'account' parameter is left undocumented, leaving one parameter with no meaning added.

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 it retrieves a single cart with full details (line items, customer, total breakdown). Differentiates from siblings like list_store_carts by specifying it returns a single cart and explicitly mentions use case of inspecting abandoned carts.

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 this tool (inspect abandoned cart before recovery email) and directs to list_store_carts for browsing cart IDs. Also notes that invalid IDs return 404, providing error handling guidance.

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