Skip to main content
Glama
damientilman

Mailchimp MCP

update_store_order_line

Update specific fields on an existing Mailchimp e-commerce order line. Only pass the fields you want to change; omitted fields remain unchanged.

Instructions

Update a line item on an existing e-commerce order.

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 order lines automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID that owns the line. line_id: Existing line item ID to update. additional_fields: Optional dict of line fields to update, merged into the body (e.g. product_id, product_variant_id, quantity, price, discount).

Returns: JSON with the updated line object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
line_idYes
order_idYes
store_idYes
additional_fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations indicate write operation; description adds partial update behavior. No mention of side effects, authorization, or idempotency details beyond annotations.

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, well-structured with brief opening, behavior explanation, Args list, and Returns. Front-loaded with purpose. No wasted text.

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 input parameters, behavior, return value, and store type context. Missing error handling or validation details, but output schema exists.

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 has 0% description coverage; description explains all parameters, especially additional_fields with examples and merge semantics. Adds significant meaning.

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?

Clearly states 'Update a line item on an existing e-commerce order.' Distinguishes from create/delete/get line item tools. Mentions store type context (custom/headless vs integrated).

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 partial update behavior ('Only the fields you pass... are changed'). Implies use for manual stores, but no explicit when-not-to-use or alternative comparisons.

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