Mailchimp MCP Server

mailchimp_ecommerce_orders_update

Update existing ecommerce order details in Mailchimp, including line items, customer info, order total, and financial status. Specify store and order IDs to apply changes.

Instructions

Update an order

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "store_id": "<store_id>",
      "order_id": "<order_id>"
    },
    "name": "mailchimp_ecommerce_orders_update"
  }
}

Input Schema

Name	Required	Description
`lines`	No	Updated line items
`customer`	No	Updated customer data
`order_id`	Yes	Order ID
`store_id`	Yes	Store ID
`order_total`	No	Updated order total
`financial_status`	No	Updated financial status

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.4/5.0

Behavior1/5

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

With no annotations, the description carries all responsibility for behavioral disclosure. 'Update an order' reveals nothing about partial vs. full updates, side effects, required identifiers, or response details. It adds no information beyond what the tool name already implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (three words), but this is under-specification rather than efficient conciseness. It omits essential context needed for correct tool invocation, so it fails to 'earn its place'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An update operation with 6 parameters and no output schema requires more than a one-line description. The description doesn't clarify how store_id and order_id are used, which fields are updatable, or what happens if optional fields are omitted. The schema covers parameter names but not the behavioral context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 6 parameters have descriptions in the schema, achieving 100% coverage. The description itself adds no parameter-level meaning, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the operation ('Update') and the resource ('an order'), making the tool's purpose unambiguous. However, it doesn't differentiate from other update tools or provide additional scope, so it doesn't reach a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool over alternatives like mailchimp_ecommerce_orders_add or mailchimp_ecommerce_orders_delete. It lacks any mention of prerequisites, context, or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server