Skip to main content
Glama
damientilman

Mailchimp MCP

update_store_order

Update fields of an existing e-commerce order in your Mailchimp store. Pass only the fields you want to change to modify financial status, fulfillment, totals, or currency.

Instructions

Update an existing e-commerce order's fields.

Only the fields you pass in additional_fields are changed; omit a field to leave it untouched. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync orders automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Existing order ID within the store. additional_fields: Optional dict of order fields to update, merged into the body (e.g. financial_status, fulfillment_status, order_total, shipping_total, currency_code).

Returns: JSON with the updated order object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
order_idYes
store_idYes
additional_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations show it's a write operation; description adds merge behavior (only changed fields) and integration caveats. Could mention side effects or error conditions.

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 two-paragraph structure: behavior first, then args. No wasted sentences.

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?

Covers merge behavior, integration context, parameter sources. Missing error handling and permission details, but output schema exists for return values.

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?

With 0% schema description coverage, the description explains store_id, order_id, and additional_fields with examples. However, the 'account' parameter is not described.

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 'Update' and the resource 'e-commerce order's fields'. It distinguishes from create, delete, and get operations among siblings.

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?

It explains when to use (partial field updates) and contrasts with automatic sync for Shopify/WooCommerce, providing context for manual vs. integrated stores.

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