Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_ecommerce_carts_list

List all abandoned carts for a store by providing the store ID. Use count and offset to control pagination.

Instructions

Get all carts (abandoned carts) for a store

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>"
    },
    "name": "mailchimp_ecommerce_carts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of records to return
offsetNoNumber of records to skip
store_idYesStore ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/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 adds the clarification that carts are abandoned carts, but fails to mention that this is a read-only operation or any potential side effects. The name implies read-only, but the description does not explicitly state it.

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 clear sentence with no redundant wording. It is appropriately sized for a simple list operation and front-loads the key information.

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?

The description tells the agent what the tool does but not what the response contains or whether any filters apply beyond store_id. Given the absence of an output schema, some return-format information would improve completeness, but the schema covers inputs and the operation is straightforward.

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 coverage is 100%, with all three parameters (count, offset, store_id) having descriptions. The tool description itself adds no parameter-specific semantics beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 identifies the tool as a list operation for ecommerce carts, specifying that 'carts' refers to abandoned carts. The verb 'Get all' and resource 'carts' distinguish it from single-cart retrieval tools like mailchimp_ecommerce_carts_get.

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

Usage Guidelines3/5

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

No explicit when-to-use guidance or alternatives are provided, but the implied usage is clear from the verb and resource. The description does not compare with related tools or mention exclusions, so it relies on the agent inferring usage from the tool name and context.

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