Skip to main content
Glama
damientilman

Mailchimp MCP

create_store_order_line

Add a product line item to an existing e-commerce order by specifying product, variant, quantity, and price. Use a unique line ID to prevent duplicates within the order.

Instructions

Add a line item to an existing e-commerce order.

line_id is client-supplied and must be unique within the order; product_id and product_variant_id must reference products that already exist in the store. 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 to add the line to. line_id: Client-supplied unique ID for the new line (e.g. 'line_1'). product_id: ID of an existing product in the store. product_variant_id: ID of an existing variant of that product. quantity: Quantity ordered. price: Unit price of the line item. additional_fields: Optional dict of extra line fields merged into the body (e.g. discount).

Returns: JSON with the created line object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priceYes
accountNo
line_idYes
order_idYes
quantityYes
store_idYes
product_idYes
additional_fieldsNo
product_variant_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations (readOnlyHint=false) are consistent with a creation operation. Description adds behavioral context: line_id uniqueness requirement, product existence prerequisite, and that it's a manual vs synced operation. No contradiction.

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?

Concise and well-structured: purpose in first sentence, context paragraph, then bulleted args. 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?

With 7 required parameters, output schema exists (though not detailed), and the description covers return format, usage context, and integration differences. No gaps for an agent to safely execute.

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 coverage is 0%, but the description thoroughly explains all 9 parameters, including the optional additional_fields and the unique constraint on line_id. The 'Args' section adds meaning beyond property names.

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 verb 'add' and resource 'line item to an existing e-commerce order,' distinguishing it from sibling tools like create_store_order (creating an order) and update_store_order_line (updating).

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?

Provides clear context: it's for custom/headless stores, while integrations sync automatically. Specifies constraints like unique line_id and existing product/variant. Lacks explicit 'when not to use' but sibling tools imply alternatives.

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