Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_ecommerce_orders_add

Add a new e-commerce order to your Mailchimp store with complete line items, customer info, and totals to sync purchase data.

Instructions

Add a new 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>",
      "id": "<id>",
      "customer": "<customer>",
      "currency_code": "<currency_code>",
      "order_total": "<order_total>",
      "lines": "<lines>"
    },
    "name": "mailchimp_ecommerce_orders_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesUnique order ID
linesYesOrder line items
customerYesCustomer information
store_idYesStore ID
campaign_idNoCampaign ID that generated this order
order_totalYesTotal order amount
currency_codeYesISO 4217 currency code
financial_statusNoFinancial status (paid, pending, etc.)
processed_at_foreignNoOrder processing time (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Add a new order' reveals only that it creates a resource, but says nothing about side effects, idempotency, required permissions, or behavior on duplicate order IDs. This is minimal even for a write operation.

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?

At one sentence, the description is technically concise, but it is under-specified for a tool with 9 parameters and nested objects. It lacks any structural cues about required fields or relationships, making it more an omission than efficient writing.

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

Completeness1/5

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

Given the tool's complexity (9 params, nested customer and lines objects) and the absence of annotations or output schema, the description is completely inadequate. It does not explain required fields, how orders relate to stores, or what the response will be, leaving the agent without sufficient context to invoke the tool correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already documents, but since the schema fully describes all 9 parameters, the description is not required to compensate.

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 'Add a new order' clearly states the action (add/create) and the resource (ecommerce order), distinguishing it from sibling tools like update, delete, list, and get. It is specific enough to be unambiguous, though it lacks any extra scope detail like 'in a specific store' that would elevate it to 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 versus alternatives. It does not mention prerequisites (e.g., needing an existing store_id), nor does it contrast with order update or delete operations. The agent must infer usage solely from the tool name.

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