Skip to main content
Glama
damientilman

Mailchimp MCP

create_store_order

Create an e-commerce order in a store by providing a unique order ID, customer details, and line items. Use for custom or headless stores.

Instructions

Create an e-commerce order in a store with a customer and line items.

order_id is client-supplied and must be unique within the store; the customer must already exist or be provided inline with the required id. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync orders automatically.

Authenticated via API key. Max 10 concurrent requests. Respects read-only and dry-run modes.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Client-supplied unique ID for the new order (e.g. 'order_42'). customer: Customer object dict. Must include 'id'; may include email_address, opt_in_status, first_name, last_name. lines: List of order line dicts. Each requires id, product_id, product_variant_id, quantity, price. additional_fields: Optional dict of extra order fields merged into the body (e.g. currency_code, order_total, financial_status, processed_at_foreign, promos). account: Optional account name (e.g. 'marketing') configured via MAILCHIMP_API_KEY_. Omit to use the default account. See list_accounts.

Returns: JSON with the created order object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesYes
accountNo
customerYes
order_idYes
store_idYes
additional_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses behavioral traits: authentication via API key, max 10 concurrent requests, respects read-only and dry-run modes. Annotations are minimal but description adds valuable context without 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?

Well-structured with clear paragraphs and bullet-style listing of args. Every sentence adds value, front-loads purpose, no redundancy. Appropriate length for the tool's complexity.

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?

Covers prerequisites, constraints (unique order_id, concurrency), authentication, mode respect, output format (JSON order object). With output schema present, description is complete for agent to use tool correctly.

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?

Adds detailed meaning beyond schema (0% coverage): explains store_id source, order_id uniqueness and example, customer required fields, lines required fields, additional_fields as optional dict, account naming convention. Significantly enhances parameter understanding.

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 creates an e-commerce order with customer and line items, using specific verbs and resource. It distinguishes from siblings like create_store_cart and create_store_order_line.

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?

Provides explicit when-to-use guidance: manual commerce vs Shopify/WooCommerce, prerequisites (customer must have id), authentication method, concurrency limit, read-only/dry-run modes. Also tells how to obtain 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