Skip to main content
Glama
damientilman

Mailchimp MCP

create_store_customer

Create a customer record in an e-commerce store and link their purchase history to an email address, with the option to subscribe them to the store's 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.

Authenticated via API key. Max 10 concurrent requests. Respects read-only and dry-run modes.

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. account: Optional account name (e.g. 'marketing') configured via MAILCHIMP_API_KEY_. Omit to use the default account. See list_accounts.

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
Behavior4/5

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

Annotations already indicate it's a write operation (readOnlyHint=false), not idempotent, not destructive. The description adds authentication requirements, concurrency limit, and respect for dry-run mode, which are useful 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.

Conciseness4/5

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

The description is well-structured with a purpose sentence, usage context, and a clear Args list. It is concise but covers necessary details. Minor redundancy in the Args section (some types already in schema) could be trimmed.

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?

Given 6 parameters and an output schema, the description adequately covers behavior, constraints, and parameter semantics. It mentions return type but could elaborate on the structure of the created customer object. Overall sufficient.

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?

The description includes a detailed Args section explaining each parameter's purpose and type, such as opt_in_status controlling subscription and additional_fields being a flexible dict. This adds significant meaning beyond the input schema's bare field names.

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, linking their purchase activity to an email address.' It specifies the action (create) and the resource (customer), and distinguishes from other store-creation tools by focusing on customer entity.

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 guidance on when to use manual writes vs automatic sync via Shopify/WooCommerce integrations, and mentions authentication and rate limits. Could be improved by explicitly contrasting with similar tools like create_store_cart or create_store_order.

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