Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

update_store_cart

Update an existing cart's totals, currency, checkout URL, or line items. Only provided fields are changed; to replace line items, pass a full lines_json array.

Instructions

Update an existing cart's totals, currency, checkout URL, or line items.

Only provided fields are changed. To replace line items, pass a full lines_json array (partial line updates are not supported by this tool — use the Mailchimp UI or REST API directly for line-level edits).

Returns 404 if store_id or cart_id is invalid.

Args: store_id: E-commerce store ID. cart_id: Existing cart ID. order_total: New order total. tax_total: New tax portion. checkout_url: New checkout URL. currency_code: New ISO 4217 currency code. lines_json: JSON string with a replacement line items array.

Returns: JSON with id, order_total, tax_total, checkout_url, currency_code, updated_at.

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>",
      "cart_id": "<cart_id>"
    },
    "name": "update_store_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
cart_idYes
store_idYes
tax_totalNo
lines_jsonNo
order_totalNo
checkout_urlNo
currency_codeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. Addedv0.5.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are all false. Description adds operational details: mutation behavior, partial update for non-line fields, and error response. Does not contradict annotations. Could mention idempotency or side effects.

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

Conciseness4/5

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

Well-structured with Args and Returns sections, uses bullet points, and is efficient. Minor redundancy with schema but overall clear and focused.

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 all parameters, return fields, and error condition. Missing details like rate limits or authentication, but given no output schema, return info is helpful. Adequate for a relatively simple update operation.

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?

With 0% schema description coverage, the description compensates fully by listing all parameters with clear, concise explanations, including the special behavior for lines_json.

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 the tool updates an existing cart, lists specific updatable fields (totals, currency, checkout URL, line items). Distinct from sibling create_store_cart and delete_store_cart.

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?

Explicitly notes that only provided fields change and that partial line-item updates are not supported, guiding users to alternative methods. Mentions 404 error for invalid IDs. Lacks explicit comparison to other tools but provides clear context.

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

Deploy Server

Other Tools