Skip to main content
Glama
damientilman

Mailchimp MCP

list_store_order_lines

Read-only

List the individual products, quantities, and prices attached to an e-commerce order to review order line items.

Instructions

List the line items of a single e-commerce order.

Use to review the individual products, quantities, and prices attached to an order. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync order lines automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID whose lines to list. count: Number of lines to return (max 1000). Defaults to 10. offset: Number of lines to skip for pagination. Defaults to 0.

Returns: JSON with lines (array of {id, product_id, product_variant_id, quantity, price, discount}), total_items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo
accountNo
order_idYes
store_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description fully aligns with annotations (readOnlyHint=true) and adds behavioral context such as pagination parameters (count max 1000, offset for skipping) and return format. No side effects are expected, and the description accurately reflects the tool's behavior.

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 concise with a clear structure: purpose, usage context, parameter list, and return format. Every sentence provides useful information 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?

The description covers all necessary aspects: purpose, parameters, return type, and usage context. The schema annotations provide full read-only safety, and the output is described. For a listing tool with a well-defined input and output, this is complete.

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?

The description adds significant meaning to 4 out of 5 parameters: explains store_id source (list_ecommerce_stores), order_id purpose, count limits, and offset for pagination. One parameter (account) is not described, but overall coverage is high and the existing descriptions add value beyond the schema.

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 'List the line items of a single e-commerce order' with a specific verb and resource. It distinguishes from sibling tools like create_store_order_line, delete_store_order_line, and get_store_order_line, as well as other order-related tools.

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 description explains when to use the tool ('review the individual products, quantities, and prices attached to an order') and provides context about manual vs automated commerce integrations. However, it does not explicitly give alternatives or when not to use it, but the context is clear.

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