Skip to main content
Glama
damientilman

Mailchimp MCP

create_store_customer

Create a new customer in a Mailchimp e-commerce store, linking their email address and purchase activity. Optionally subscribe them to the connected audience.

Instructions

Create a customer in a store, linking their purchase activity to an email address.

The opt_in_status controls whether the customer is added to the store's connected audience as a subscriber. Many stores sync customers automatically via Shopify or WooCommerce integrations; these manual writes suit custom or headless storefronts.

Args: store_id: E-commerce store ID. customer_id: Client-supplied unique ID for the new customer. email_address: Customer's email address. opt_in_status: Whether to subscribe the customer to the connected audience (bool). additional_fields: Optional dict of extra documented fields (e.g. first_name, last_name, company, address) merged into the request body.

Returns: JSON with the created customer object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
store_idYes
customer_idYes
email_addressYes
opt_in_statusYes
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 readOnlyHint=false (write operation), idempotentHint=false, destructiveHint=false. The description adds context such as linking purchase activity and opt_in behavior, but does not mention idempotency, error handling for duplicate customer_id, or authentication requirements. It covers some traits but leaves gaps.

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?

The description is well-structured with a purpose sentence, context, and Args/Returns list. It is front-loaded and each sentence serves a purpose, though a bit lengthy. No wasteful repetition.

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

Completeness3/5

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

Given the complexity (6 parameters, no schema descriptions) and presence of output schema, the description covers purpose, usage context, returns, and most parameters. However, it misses the 'account' parameter and could clarify uniqueness constraints. It is mostly complete but not fully comprehensive.

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 has 0% description coverage, so the description must compensate. It describes 4 of 6 parameters explicitly (store_id, customer_id, email_address, opt_in_status) and adds detail for additional_fields with examples. The account parameter is entirely omitted, and the descriptions for main parameters only restate names, adding minimal semantic value beyond the schema.

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 'Create a customer in a store' with a specific verb and resource. It also explains the opt_in_status purpose and distinguishes from automatic sync via Shopify/WooCommerce, aiding differentiation from other tools like create_store_cart or create_store_order.

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 states when to use this tool: 'manual writes suit custom or headless storefronts' and implies not to use when automatic sync is active. However, it does not name specific alternative tools or provide explicit exclusion scenarios, so it's slightly below top score.

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