Skip to main content
Glama
Mailchimp MCP

Mailchimp MCP

by damientilman

Mailchimp MCP Server

CI PyPI version PyPI downloads License: MIT Python 3.10+ MCP Docker

The most complete Model Context Protocol (MCP) server for the Mailchimp Marketing API: 259 tools to query and manage your Mailchimp account from any MCP-compatible client. It covers the full campaign, audience, member, segment, automation and reporting surface, complete e-commerce (read and write), landing pages, File Manager, surveys, signup forms and verified domains, plus multi-account support and runtime-security guardrails (read-only, dry-run and audit modes, with per-tool risk metadata).

Uses the Mailchimp Marketing API via requests. Not based on the official mailchimp-marketing-python client. I hit too many issues with it so I went with raw HTTP calls instead.

Quick start

uvx mailchimp-mcp   # no install required; just needs MAILCHIMP_API_KEY

Add it to your MCP client (Claude Desktop, Cursor, Cline, …):

{
  "mcpServers": {
    "mailchimp": {
      "command": "uvx",
      "args": ["mailchimp-mcp"],
      "env": {
        "MAILCHIMP_API_KEY": "your-key-us8",
        "MAILCHIMP_READ_ONLY": "true"
      }
    }
  }
}

Tip: start with MAILCHIMP_READ_ONLY=true to explore safely, then flip it off when you are ready to write. See Configuration for all options.

Docker

A prebuilt image is published to the GitHub Container Registry on every release:

docker run --rm -i -e MAILCHIMP_API_KEY=your-key-us8 ghcr.io/damientilman/mailchimp-mcp-server:latest

Or point your MCP client at it:

{
  "mcpServers": {
    "mailchimp": {
      "command": "docker",
      "args": ["run", "--rm", "-i", "-e", "MAILCHIMP_API_KEY", "-e", "MAILCHIMP_READ_ONLY", "ghcr.io/damientilman/mailchimp-mcp-server:latest"],
      "env": {
        "MAILCHIMP_API_KEY": "your-key-us8",
        "MAILCHIMP_READ_ONLY": "true"
      }
    }
  }
}

Related MCP server: Mailchimp MCP Server

Features

Read

  • Campaigns - List, search, and inspect campaign details

  • Reports - Open/click rates, bounces, per-link clicks, domain performance, unsubscribe details

  • Email activity - Per-recipient open/click tracking, member activity history

  • Audiences - Browse audiences, members, segments, tags, and growth history

  • Merge fields - List custom fields for an audience

  • Interest categories & groups - Browse interest categories and options

  • Webhooks - List configured webhooks

  • Segments - Get segment details, conditions, and member lists

  • Automations - List workflows, inspect emails in a workflow, view queues

  • Templates - Browse templates and extract HTML content

  • Landing pages - List and inspect landing pages

  • File Manager - Browse stored images and files, and folders

  • Surveys - List and inspect an audience's surveys

  • Signup forms - Inspect an audience's signup forms

  • E-commerce - Stores, orders, products, customers (requires e-commerce integration)

  • Campaign folders - Browse folder organization

  • Batch operations - Monitor bulk operation status

Write

  • Members - Add, update, unsubscribe, delete, and tag contacts

  • Audiences - Batch subscribe members, update audience settings

  • Campaigns - Create drafts, set HTML content, schedule, unschedule, duplicate, delete, send, send test, cancel

  • Segments/Tags - Create, update, delete, add/remove members, dynamic conditions

  • Merge fields - Create, update, delete custom fields

  • Interest categories - Create and delete categories and interests

  • Webhooks - Create and delete webhooks

  • Templates - Create, update, and delete email templates

  • File Manager - Upload (base64) and delete images and files

  • Surveys - Publish and unpublish audience surveys

  • Signup forms - Customize header, contents, and styles

  • Automations - Pause and start automation workflows

  • E-commerce - Cart lifecycle, promo rules, and promo codes for discount workflows

  • Batch - Run bulk API operations in a single request

Runtime security

  • Risk metadata - Per-tool read / write / destructive classification via MCP annotations and describe_tools

  • Audit log - Optional structured JSON audit events per dispatch (MAILCHIMP_AUDIT_LOG)

  • Argument validation - Pagination caps and required-ID checks before every request

Prerequisites

Installation

Using uvx (recommended)

No installation needed — run directly:

uvx mailchimp-mcp

Using pip

pip install mailchimp-mcp

Then run:

mailchimp-mcp

From source

git clone https://github.com/damientilman/mailchimp-mcp-server.git
cd mailchimp-mcp-server
python -m venv .venv
source .venv/bin/activate
pip install -e .

Configuration

Variable

Required

Description

MAILCHIMP_API_KEY

Yes

Your Mailchimp API key (format: <key>-<dc>, e.g. abc123-us8)

MAILCHIMP_READ_ONLY

No

Set to true to disable all write operations (default: false)

MAILCHIMP_DRY_RUN

No

Set to true to preview write operations without executing them (default: false)

MAILCHIMP_API_KEY_<NAME>

No

API key for an additional named account (e.g. MAILCHIMP_API_KEY_MARKETING). Target it with the account argument. See Multi-account.

MAILCHIMP_READ_ONLY_<NAME>

No

Read-only mode for a specific named account (default: false)

MAILCHIMP_DRY_RUN_<NAME>

No

Dry-run mode for a specific named account (default: false)

MAILCHIMP_AUDIT_LOG

No

Set to true to emit a structured JSON audit event per tool dispatch to stderr (default: false). See Runtime security.

MAILCHIMP_TOOLS

No

Expose only a subset of tools to shrink the model's tool-list footprint (default: all). See Tool profiles.

The datacenter (us8, us21, etc.) is automatically extracted from each key.

Safety modes

Read-only mode — When MAILCHIMP_READ_ONLY=true, all write tools (create, update, delete, schedule, etc.) are blocked and return an error. Read tools work normally. This is the recommended default for shared or exploratory setups where you only need reporting and analytics.

Dry-run mode — When MAILCHIMP_DRY_RUN=true, write tools return a preview of the action they would perform (tool name, target resource, parameters, and its risk tier) without making any API call. Useful for testing prompts before going live.

Runtime security

The server is designed for defense-in-depth alongside an external MCP gateway: it owns the semantics (which tools are reads, reversible writes, or irreversible) and exposes them as machine-readable signals a gateway can enforce on, rather than making the gateway guess which calls are dangerous.

Risk metadata — Every tool is classified as read, write, or destructive (irreversible data loss or an irreversible send). This surfaces two ways:

  • MCP tool annotations — readOnlyHint, destructiveHint, and idempotentHint travel through the standard tools/list, so any compliant client or gateway reads them directly.

  • describe_tools — a read tool returning {name, risk, read_only, destructive, idempotent} for every tool plus per-tier counts, for gateways that prefer a tool call.

Structured audit log — With MAILCHIMP_AUDIT_LOG=true, each dispatch emits one JSON event to stderr with the tool, its risk tier, the destructive flag, the target account, the outcome (executed / blocked_read_only / dry_run), and the inspected arguments. Bulky or sensitive values (e.g. base64 file_data) are redacted and response bodies are never logged, so the stream is a safe audit sink to tail centrally.

Argument-contract validation — All writes funnel through a single _guard_write chokepoint, and every request is validated before dispatch (pagination count capped to 1–1000, missing path IDs rejected), so malformed calls fail fast and consistently instead of hitting the API.

Tool profiles

Exposing all 259 tools sends a large tool list to the model on every turn (~63k tokens). If you only need part of the surface, load a subset with one line:

"env": { "MAILCHIMP_API_KEY": "your-key-us8", "MAILCHIMP_TOOLS": "read" }

MAILCHIMP_TOOLS accepts a comma-separated mix of risk tiers (read, write, destructive) and/or exact tool names; a tool is kept if either matches. Unset (or all) exposes everything.

  • read — reporting and analytics only (~115 tools, ~29k tokens). A safe, lightweight default for exploration.

  • read,write — everything except irreversible tools.

  • list_campaigns,get_campaign_report,send_campaign — a hand-picked minimal set.

Tool descriptions are also trimmed of repeated boilerplate before they reach the model, so even the full set is leaner than the raw docstrings. Use describe_tools to see each tool's risk tier.

Multi-account

By default the server uses the single MAILCHIMP_API_KEY, exposed as the default account. To manage several Mailchimp accounts from one server, add MAILCHIMP_API_KEY_<NAME> variables — the suffix becomes the lowercased account name (e.g. MAILCHIMP_API_KEY_MARKETING → marketing).

Every tool then accepts an optional account argument, e.g. list_audiences(account="marketing"). Selection is per call and stateless — there is no "current account" to switch, so a write always names its target. Omitting account uses default. Call list_accounts to see the configured names and their safety-flag state, and each account can carry its own MAILCHIMP_READ_ONLY_<NAME> / MAILCHIMP_DRY_RUN_<NAME> flags (so a write-protected account and a writable one can live side by side). An unknown account returns an error listing the configured names.

Single-key setups are unaffected: with only MAILCHIMP_API_KEY set, nothing changes.

{
  "mcpServers": {
    "mailchimp": {
      "command": "uvx",
      "args": ["mailchimp-mcp"],
      "env": {
        "MAILCHIMP_API_KEY": "your-default-key-us8",
        "MAILCHIMP_API_KEY_MARKETING": "another-key-us5",
        "MAILCHIMP_READ_ONLY_MARKETING": "true"
      }
    }
  }
}

MCP client configuration

Most MCP clients accept a JSON configuration block describing how to launch the server. Configure yours to invoke uvx mailchimp-mcp (or mailchimp-mcp if installed via pip) with MAILCHIMP_API_KEY exported in the environment.

{
  "mcpServers": {
    "mailchimp": {
      "command": "uvx",
      "args": ["mailchimp-mcp"],
      "env": {
        "MAILCHIMP_API_KEY": "your-api-key-here"
      }
    }
  }
}
{
  "mcpServers": {
    "mailchimp": {
      "command": "mailchimp-mcp",
      "env": {
        "MAILCHIMP_API_KEY": "your-api-key-here"
      }
    }
  }
}
{
  "mcpServers": {
    "mailchimp": {
      "command": "uvx",
      "args": ["mailchimp-mcp"],
      "env": {
        "MAILCHIMP_API_KEY": "your-api-key-here",
        "MAILCHIMP_READ_ONLY": "true"
      }
    }
  }
}

CLI-based clients

If your MCP client provides a CLI to register servers, the equivalent invocation is:

mcp-cli add mailchimp \
  -e MAILCHIMP_API_KEY=your-api-key-here \
  -- uvx mailchimp-mcp

Replace mcp-cli with your client's binary name. For read-only mode, add -e MAILCHIMP_READ_ONLY=true to the command.

Available Tools

Account

Tool

Description

get_account_info

Get account name, email, and subscriber count

list_accounts

List configured accounts and their read-only / dry-run state (for multi-account setups)

describe_tools

List every tool with its risk tier (read / write / destructive) for policy enforcement

Campaigns (read)

Tool

Description

list_campaigns

List campaigns with optional filters (status, date)

get_campaign_details

Get full details of a specific campaign

list_campaign_folders

List campaign folders

Campaign Reports

Tool

Description

get_campaign_report

Get performance metrics (opens, clicks, bounces)

get_campaign_click_details

Get per-link click data for a campaign

get_email_activity

Per-recipient activity (opens, clicks, bounces)

get_open_details

Who opened, when, how many times

get_campaign_recipients

List of recipients with delivery status

get_campaign_unsubscribes

Who unsubscribed after a campaign

get_domain_performance

Performance by email domain (gmail, outlook, etc.)

get_ecommerce_product_activity

Revenue per product for a campaign

get_campaign_sub_reports

Sub-reports (A/B tests, RSS, etc.)

get_campaign_advice

Mailchimp's automated post-send feedback on a campaign

get_campaign_locations

Geographic open data (country, region)

get_eepurl_activity

Social sharing stats (Twitter, Facebook, referrers)

Campaigns (write)

Tool

Description

create_campaign

Create a new campaign draft (regular or A/B variate, with optional segment targeting)

update_campaign

Update settings or segment targeting of a campaign

set_campaign_content

Set the HTML content of a campaign draft

schedule_campaign

Schedule a campaign for a specific date/time

unschedule_campaign

Unschedule a campaign (back to draft)

replicate_campaign

Duplicate an existing campaign

delete_campaign

Delete an unsent campaign

send_campaign

Send a campaign immediately

send_test_email

Send a test email for a campaign

cancel_send

Cancel a campaign that is currently sending

Audiences (read)

Tool

Description

list_audiences

List all audiences with stats, opt-in mode, GDPR flag, and sender defaults

get_audience_details

Get detailed info for a specific audience

list_audience_members

List members with optional status filter

search_members

Search members by email or name

get_audience_growth_history

Monthly growth data (subscribes, unsubscribes)

Members (read)

Tool

Description

get_member_activity

Activity history of a specific contact

get_member_tags

All tags assigned to a contact

get_member_events

Custom events for a contact

list_member_notes

List CRM-style internal notes attached to a contact

Members (write)

Tool

Description

add_member

Add a new contact to an audience

update_member

Update a contact's name or status

unsubscribe_member

Unsubscribe a contact

delete_member

Permanently delete a contact

tag_member

Add or remove tags from a contact

add_member_note

Attach a CRM-style internal note to a contact

update_member_note

Update the text of an existing member note

delete_member_note

Delete a member note

Audiences (write)

Tool

Description

batch_subscribe

Batch add/update multiple members in an audience

update_audience

Update audience settings (name, defaults, permission reminder)

create_audience

Create a new audience with contact info and campaign defaults

delete_audience

Permanently delete an audience and all its data

Segments & Tags

Tool

Description

list_segments

List segments and tags for an audience

get_segment

Get segment details including conditions

list_segment_members

List members in a segment

create_segment

Create a new segment or tag (static or dynamic with conditions)

update_segment

Update a segment's name or conditions

delete_segment

Delete a segment or tag

add_members_to_segment

Add contacts to a segment/tag

remove_members_from_segment

Remove contacts from a segment/tag

Merge Fields

Tool

Description

list_merge_fields

List custom fields for an audience

create_merge_field

Create a new custom field (text, number, dropdown, etc.)

update_merge_field

Update a custom field

delete_merge_field

Delete a custom field

Interest Categories & Groups

Tool

Description

list_interest_categories

List interest categories for an audience

create_interest_category

Create a new interest category

list_interests

List interests within a category

create_interest

Create a new interest option

delete_interest_category

Delete an interest category

delete_interest

Delete an interest option

Webhooks

Tool

Description

list_webhooks

List webhooks for an audience

create_webhook

Create a new webhook

delete_webhook

Delete a webhook

Automations & Customer Journeys

Tool

Description

list_automations

List Classic Automation workflows (Customer Journeys are not exposed by Mailchimp's API)

get_automation_emails

List emails in a Classic workflow

get_automation_email_queue

View the send queue for an automation email

pause_automation

Pause all emails in a Classic workflow

start_automation

Start/resume all emails in a Classic workflow

trigger_customer_journey

Enroll a contact into a Customer Journey step (the only journey write Mailchimp exposes)

search_automation_campaigns

List campaigns emitted by either Classic Automations or Customer Journeys

get_member_journey_events

Filter a member's activity feed to automation/journey-related events

get_automation_summary

Combined overview: Classic workflows by status + recent automation send volume

Mailchimp does not expose a public read API for Customer Journeys (only the trigger endpoint above). The search_automation_campaigns, get_member_journey_events and get_automation_summary tools provide the recommended workarounds — they surface every campaign emitted by automations or journeys, even though the journey graph itself remains private.

Templates

Tool

Description

list_templates

List available email templates

get_template

Get template metadata (name, type, dates, thumbnail)

get_template_default_content

Get template HTML content

create_template

Create a new email template

update_template

Update template name or HTML

delete_template

Delete a user-created template

Landing Pages

Tool

Description

list_landing_pages

List all landing pages

get_landing_page

Get details of a landing page

create_landing_page

Create a new landing page from a template

update_landing_page

Update settings of an existing landing page

delete_landing_page

Permanently delete a landing page

publish_landing_page

Publish a landing page to its public URL

unpublish_landing_page

Take a published landing page offline

File Manager

Tool

Description

list_files

List images and files stored in the File Manager

get_file

Get a single file's metadata and hosted URL

upload_file

Upload a new image or file (base64-encoded)

delete_file

Permanently delete a file

list_file_folders

List File Manager folders

Surveys

Tool

Description

list_surveys

List an audience's surveys with status and public URL

get_survey

Get a single survey's full details

publish_survey

Publish a survey to its public URL

unpublish_survey

Take a published survey offline

Signup Forms

Tool

Description

list_signup_forms

Get the signup forms configured for an audience

customize_signup_form

Customize a signup form's header, contents, and styles

E-commerce

Tool

Description

list_ecommerce_stores

List connected e-commerce stores

list_store_orders

List orders from a store

list_store_products

List products from a store

list_store_customers

List customers from a store

E-commerce Carts

Tool

Description

list_store_carts

List carts (including abandoned) for a store

get_store_cart

Get a single cart with full line items

create_store_cart

Push a cart (e.g. an abandoned cart from an external system)

update_store_cart

Update a cart's totals, currency, checkout URL, or line items

delete_store_cart

Permanently delete a cart

E-commerce Promo Rules & Codes

Tool

Description

list_promo_rules

List discount rules for a store

get_promo_rule

Get a single promo rule's configuration

create_promo_rule

Create a discount rule (fixed amount, percentage, free shipping)

update_promo_rule

Update a rule's amount, target, dates, or enabled state

delete_promo_rule

Permanently delete a rule and all its codes

list_promo_codes

List redeemable codes attached to a rule

get_promo_code

Get a single promo code with usage stats

create_promo_code

Create a redeemable code (e.g. 'SUMMER20') under a rule

update_promo_code

Update a code's string, redemption URL, or enabled state

delete_promo_code

Permanently delete a promo code

Batch Operations

Tool

Description

create_batch

Run multiple API operations in bulk

get_batch_status

Check status of a batch operation

list_batches

List recent batch operations

list_batch_webhooks

List batch-completion webhooks

get_batch_webhook

Get a single batch webhook

create_batch_webhook

Create a batch-completion webhook

update_batch_webhook

Update a batch webhook's URL

delete_batch_webhook

Delete a batch webhook

Verified Domains

Tool

Description

list_verified_domains

List sending domains and their verification state

get_verified_domain

Get a single sending domain's record

create_verified_domain

Start verification for a sending domain

verify_verified_domain

Complete verification with the emailed code

delete_verified_domain

Remove a verified sending domain

Connected Sites & Account

Tool

Description

list_connected_sites

List connected sites for tracking and pop-ups

get_connected_site

Get a single connected site with its script

create_connected_site

Connect a website and generate its script

delete_connected_site

Remove a connected site

verify_connected_site_script

Verify the tracking script is installed

list_authorized_apps

List OAuth-authorized applications

get_authorized_app

Get a single authorized application

get_chimp_chatter

Read the account activity feed

list_account_exports

List account data export jobs

get_account_export

Get an export job's status and download URL

create_account_export

Start an account data export

Folders

Tool

Description

create_campaign_folder

Create a campaign folder

get_campaign_folder

Get a single campaign folder

update_campaign_folder

Rename a campaign folder

delete_campaign_folder

Delete a campaign folder

list_template_folders

List template folders

get_template_folder

Get a single template folder

create_template_folder

Create a template folder

update_template_folder

Rename a template folder

delete_template_folder

Delete a template folder

Campaign Extras (checklist, collaboration, RSS)

Tool

Description

get_campaign_send_checklist

Pre-send readiness checklist

list_campaign_feedback

List team collaboration comments

get_campaign_feedback

Get a single comment

create_campaign_feedback

Add a collaboration comment

update_campaign_feedback

Edit a comment

delete_campaign_feedback

Delete a comment

pause_rss_campaign

Pause an RSS-driven campaign

resume_rss_campaign

Resume an RSS-driven campaign

Audience Insights & Deliverability

Tool

Description

get_audience_activity

Recent daily activity for an audience

get_audience_top_locations

Top countries of an audience

get_audience_clients

Top email clients used by an audience

list_audience_abuse_reports

Spam complaints for an audience

get_audience_abuse_report

A single audience abuse report

Members (compliance & advanced)

Tool

Description

upsert_member

Add-or-update a member idempotently (PUT)

delete_member_permanent

GDPR permanent erasure of a member

get_member_goals

A member's recent tracked goal events

add_member_event

Record a custom event on a member

Automation Emails (single-email control)

Tool

Description

get_automation_email

Get one email in a classic automation

pause_automation_email

Pause a single automation email

start_automation_email

Start a single automation email

add_automation_queue_subscriber

Enqueue a subscriber for an automation email

get_automation_queue_subscriber

Get a subscriber's queue status

list_automation_removed_subscribers

List subscribers removed from a workflow

remove_automation_subscriber

Remove a subscriber from a workflow

get_automation_removed_subscriber

Get a single removed subscriber

Reporting (extras)

Tool

Description

get_campaign_sent_to

Per-recipient delivery status for a campaign

get_campaign_abuse_reports

Spam complaints for a campaign

get_campaign_abuse_report

A single campaign abuse report

list_landing_page_reports

Reports across all landing pages

get_landing_page_report

Report for a single landing page

list_survey_reports

Reports across all surveys

get_survey_report

Report for a single survey

get_survey_responses

List a survey's responses

get_survey_response

Get a single survey response

get_survey_questions_report

Per-question survey report

get_survey_question_answers

Answers for a single survey question

E-commerce (write)

Tool

Description

create_store / get_store / update_store / delete_store

Store lifecycle

get_store_product / create_store_product / update_store_product / delete_store_product

Product lifecycle

list_store_product_variants / get_store_product_variant / create_store_product_variant / update_store_product_variant / delete_store_product_variant

Product variants

list_store_product_images / get_store_product_image / create_store_product_image / update_store_product_image / delete_store_product_image

Product images

get_store_order / create_store_order / update_store_order / delete_store_order

Order lifecycle

list_store_order_lines / get_store_order_line / create_store_order_line / update_store_order_line / delete_store_order_line

Order line items

get_store_customer / create_store_customer / update_store_customer / delete_store_customer

Customer lifecycle

list_account_orders

List orders across every store

Example Prompts

Once connected, you can ask your MCP client to perform requests like:

  • "Show me all my sent campaigns from the last 3 months"

  • "What was the open rate and click rate for my last newsletter?"

  • "How many subscribers did I gain this year?"

  • "Which links got the most clicks in campaign X?"

  • "Search for subscriber john@example.com"

  • "Add tag 'VIP' to all members who opened my last campaign"

  • "Create a draft campaign for my main audience with subject 'March Update'"

  • "Create a campaign targeting only my VIP segment"

  • "Send a test email of my draft campaign to test@example.com"

  • "List all merge fields for my main audience"

  • "Create a dropdown merge field called 'Industry' with options Tech, Finance, Healthcare"

  • "Create a dynamic segment of members where FNAME is John"

  • "Batch subscribe 50 members from this CSV data"

  • "Set up a webhook to notify my app when new subscribers join"

  • "Unsubscribe user@example.com from my list"

  • "Show me the domain performance breakdown for my last campaign"

  • "Where in the world did people open my newsletter? Show me the geographic breakdown."

  • "Create an A/B test campaign with two subject lines and pick the winner by opens after 24 hours"

  • "What advice does Mailchimp have for improving my last campaign?"

  • "Pause my welcome automation"

  • "List all orders from my Shopify store this month"

Workflow recipes

Multi-step requests that chain tools end to end:

  • Weekly performance review — "Summarise my last week: list campaigns sent since Monday, pull each report, and rank them by click rate with one takeaway each." Chains search_campaigns → get_campaign_report → get_campaign_advice.

  • Deliverability audit — "Check my sending health: are my domains verified, any spam complaints on recent campaigns, and how did the last one perform by recipient domain?" Chains list_verified_domains → get_campaign_abuse_reports → get_domain_performance.

  • Re-engagement — "Find everyone who didn't open my last newsletter and resend it with a new subject line." Chains get_campaign_report → resend_to_non_openers.

  • Safe send — "Dry-run a campaign to my VIP segment, show me the send checklist, then send it once I confirm." With MAILCHIMP_DRY_RUN=true, previews via create_campaign → get_campaign_send_checklist → send_campaign.

  • Agencies (multi-account) — "For both the acme and globex accounts, list this month's top campaign by open rate." Passes account="acme" / account="globex" per call. See Multi-account.

Contributing

Contributions are welcome. See CONTRIBUTING.md for development setup, test instructions, and pull request guidelines.

Security

If you find a security vulnerability, please follow the responsible disclosure process described in SECURITY.md.

Changelog

See CHANGELOG.md for the full release history.

Author

Built by Damien Tilman — damien@tilman.marketing

License

MIT — see LICENSE for details.

Available Tools

227 tools
add_automation_queue_subscriberA

Add a subscriber to the queue of a classic automation email.

Manually enrolls a subscriber into the sending queue for a specific automation email. The subscriber will receive the email as part of the workflow once processed.

Args: workflow_id: The unique id of the classic automation workflow. workflow_email_id: The unique id of the automation email whose queue to add to. email_address: The email address of the subscriber to enqueue.

Returns: JSON describing the queued subscriber.

Inputs: workflow_id (required), email_address (required), workflow_email_id (required), account. Returns: result

add_memberA

Add a new member to an audience with optional name and tags.

Creates a new contact. Returns "Member Exists" error if already present. Choose the right member tool: add_member for new contacts, update_member to change profile/status of existing contacts, tag_member to manage tags on existing contacts, batch_subscribe for bulk add/update (up to 500), unsubscribe_member to opt out, delete_member for permanent GDPR removal. Side effect: status='pending' triggers a double opt-in confirmation email.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the new member. Must not already exist in the audience. status: 'subscribed' (default), 'pending' (triggers opt-in email), 'unsubscribed', 'cleaned'. first_name: First name (FNAME merge field). last_name: Last name (LNAME merge field). tags: Comma-separated tag names (e.g. 'VIP,Newsletter'). Created automatically if new.

Returns: JSON with id (MD5 hash of email), email_address, status, full_name.

Inputs: list_id (required), email_address (required), tags, status, +3 more. Returns: result

add_member_eventA

Record a custom event for an audience member (e.g. 'purchased', 'viewed_pricing').

Use to log member activity that can trigger automations or power segmentation. Use get_member_events to read a member's recorded events and get_member_goals for tracked Goals.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: The member's email address. The subscriber hash is derived automatically. name: Event name (letters, numbers, underscores; max 30 chars, e.g. 'purchased'). properties: Optional dict of custom key/value properties describing the event.

Returns: JSON confirming the event was recorded, or an error object if the member is not found or the input is rejected. On success the Mailchimp API returns an empty body (HTTP 204).

Inputs: name (required), list_id (required), email_address (required), account, +1 more. Returns: result

add_member_noteA

Add a CRM-style internal note to a member. Not sent to the contact.

Useful for sales/support context, e.g. "Asked for discount on annual plan", "Out of office until June 1st". Use update_member_note to edit an existing note instead of adding another.

Returns 404 if the member does not exist; returns 400 if note text exceeds 1000 chars.

Args: list_id: Audience/list ID. Obtain from list_audiences. email_address: Email of the member to attach the note to. Must exist in the audience. note: Note text (max 1000 chars). Plain text; markdown is not rendered in the Mailchimp UI.

Returns: JSON with id (use as note_id), email_address, note, created_at, created_by.

Inputs: note (required), list_id (required), email_address (required), account. Returns: result

add_members_to_segmentA

Add members to a static segment or tag by email address.

Only works on static segments (tags), not dynamic segments. Members must already exist in the audience. Use tag_member for single-member tag management instead.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. segment_id: Static segment/tag ID (numeric string, e.g. '12345'). Obtain from list_segments. emails: Comma-separated emails to add (e.g. 'a@co.com,b@co.com'). Must exist in audience.

Returns: JSON with total_added, total_removed (always 0), errors array.

Inputs: emails (required), list_id (required), segment_id (required), account. Returns: result

batch_subscribeA

Add or update up to 500 members in a single synchronous request.

Use for bulk operations. Choose the right member tool: batch_subscribe for 2-500 members, add_member or update_member for a single member, create_batch for imports larger than 500. Side effect: members with status='pending' each receive a double opt-in confirmation email.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. members_json: JSON array of members (max 500). Each requires email_address and status ('subscribed'/'unsubscribed'/'cleaned'/'pending'). Optional: merge_fields, tags. update_existing: If true (default), existing members are updated. If false, skipped as errors.

Returns: JSON with new_members, updated_members, errors array, total_created, total_updated, error_count.

Inputs: list_id (required), members_json (required), account, update_existing. Returns: result

cancel_sendA

Cancel a campaign mid-send, stopping delivery to remaining recipients.

Only works on campaigns with status 'sending'. Already-delivered emails cannot be recalled. Irreversible. Use unschedule_campaign for scheduled (not yet sending) campaigns instead.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be in 'sending' status.

Returns: JSON with status ("cancelled"), campaign_id. Error if not currently sending.

Inputs: campaign_id (required), account. Returns: result

create_account_exportA

Start an account export job covering the requested categories of account data.

Use to request a downloadable archive of account data; poll get_account_export until the status is finished, then read download_url. Use list_account_exports to check existing exports before starting a new one.

Args: include_stages: List of stage names to include in the export (e.g. ['lists', 'campaigns', 'reports', 'ecommerce']). Each named category is added to the export archive.

Returns: JSON with export_id, status, started (ISO 8601), finished (ISO 8601 or null), size_in_bytes, download_url.

Inputs: include_stages (required), account. Returns: result

create_audienceA

Create a new audience (list) with required contact info, campaign defaults, and permission reminder.

Side effect: creates a billable audience under the Mailchimp plan. Mailchimp requires all contact fields (company, address, city, state, zip, country) and CAN-SPAM-compliant permission reminder text. Use update_audience to modify later, delete_audience for cleanup, or list_audiences to verify creation.

Returns 400 error if any required field is missing or the plan audience limit is reached.

Args: name: Audience display name shown in dashboard and audience picker (max 100 chars). from_name: Default sender name on campaigns (e.g. 'Marketing Team'). Max 100 chars. from_email: Default sender email. Must be on a verified sending domain. subject: Default subject line for new campaigns. Max 150 chars. language: Default language code (e.g. 'en', 'fr', 'es'). ISO 639-1 two-letter code. company: Legal company name displayed in email footer (required by CAN-SPAM). address1: Primary postal address line shown in email footer. city: City of the postal address. state: State or region of the postal address. zip: Postal/ZIP code. country: Two-letter ISO country code (e.g. 'US', 'FR', 'GB'). permission_reminder: Sentence shown at the bottom of every email explaining why subscribers receive it (required by CAN-SPAM). email_type_option: If true, lets subscribers choose plaintext vs. HTML emails. Default false. address2: Optional secondary postal address line. phone: Optional contact phone number shown in the footer.

Returns: JSON with id (new list_id, save for subsequent calls), name, member_count (0 at creation), date_created, subscribe_url_short.

Inputs: zip (required), city (required), name (required), state (required), +12 more. Returns: result

create_batchA
Destructive

Submit multiple API operations as a single asynchronous batch request.

Use for bulk operations exceeding other tool limits (e.g. batch_subscribe max 500). Operations run asynchronously; poll with get_batch_status. Each operation runs independently. Because a batch can wrap arbitrary DELETEs, this tool is classified destructive so a gateway treats it with the same caution as a delete.

Args: operations: JSON array of operations. Each requires: method ('GET'/'POST'/'PATCH'/'PUT'/ 'DELETE'), path (API endpoint, e.g. '/lists/abc123/members'), optional body (JSON string).

Returns: JSON with id (batch ID for get_batch_status), status ('pending'), total_operations, submitted_at.

Inputs: operations (required), account. Returns: result

create_batch_webhookA

Create a new batch webhook that notifies a URL when batch operations complete.

Use to receive callbacks when batch jobs finish instead of polling get_batch_status. Use update_batch_webhook to change the URL later and delete_batch_webhook to remove it.

Args: url: The callback URL Mailchimp will POST to when a batch completes (must be publicly reachable).

Returns: JSON with id (new batch_webhook_id), url, enabled (boolean). Returns an error object if the URL is rejected.

Inputs: url (required), account. Returns: result

create_campaignA

Create a new email campaign in draft status, with optional segment targeting or A/B variate testing.

Typical workflow: create_campaign -> set_campaign_content (add HTML body) -> send_test_email (preview) -> send_campaign or schedule_campaign (deliver). The campaign is created in 'save' (draft) status and cannot be sent until content is set. Use replicate_campaign instead to clone an existing campaign.

For A/B testing, set campaign_type='variate' and pass variate_settings_json describing the test. Mailchimp will send variants to a sample of recipients, then auto-pick a winner based on winner_criteria and send it to the remaining audience after wait_time.

Args: list_id: The audience/list ID to send to (e.g. 'abc123def4'). Obtain from list_audiences. subject_line: Subject line recipients see in their inbox. Keep under 150 chars. For variate campaigns testing subject lines, this is the default/fallback. title: Internal title for organizing in Mailchimp dashboard. Defaults to subject_line if omitted. preview_text: Preheader text shown after the subject line in inbox. Keep under 200 chars. from_name: Sender name on the email. Falls back to audience default if omitted. reply_to: Reply-to email address. Must be a verified domain. Falls back to audience default. segment_id: Saved segment ID to restrict recipients. Only members matching this segment receive the email. Obtain from list_segments. Omit to send to the full audience. campaign_type: 'regular' (default) for a standard campaign, or 'variate' for an A/B test. 'plaintext', 'rss', and 'absplit' (legacy A/B) are also accepted but rarely used. variate_settings_json: Required when campaign_type='variate'. JSON string with keys: winner_criteria ('opens' | 'clicks' | 'manual' | 'total_revenue'), test_size (10-100, percent of audience sampled), wait_time (minutes before picking winner), and one of subject_lines (list of 2-8 strings), from_names (list of 2-8), reply_to_addresses (list of 2-8), send_times (list of 2-8 ISO datetimes), or contents (list of 2-8 HTML strings). Example: '{"winner_criteria": "opens", "test_size": 20, "wait_time": 1440, "subject_lines": ["Spring Sale 20% off", "Last chance: 20% off Spring"]}'

Returns: JSON with fields: id (string, the new campaign ID for use with set_campaign_content, send_campaign, etc.), status ('save'), title, subject_line, web_id (int, for Mailchimp web UI link), type. Returns error if list_id is invalid, variate_settings_json is malformed, or variate settings violate Mailchimp constraints.

Example: create_campaign(list_id="abc123", subject_line="Spring Sale", preview_text="20% off") -> {"id": "def456", "status": "save", "type": "regular", ...}

Inputs: list_id (required), subject_line (required), title, account, +6 more. Returns: result

create_campaign_feedbackA

Add a team collaboration feedback comment to a campaign.

Use to leave review notes for teammates during campaign preparation. Optionally attach the comment to a specific content block via block_id. Use list_campaign_feedback to review existing comments.

Args: campaign_id: Campaign ID to comment on. Obtain from list_campaigns or search_campaigns. message: The feedback comment text. block_id: Optional content block ID to attach the comment to.

Returns: JSON with feedback_id, message, is_complete, block_id, created_by, created_at.

Inputs: message (required), campaign_id (required), account, block_id. Returns: result

create_campaign_folderA

Create a new folder to organize campaigns.

Use to group related campaigns (e.g. by client, month, or theme) for easier navigation. Assign campaigns to the folder via the folder_id field when creating or updating them. Use list_campaign_folders to browse existing folders.

Args: name: Display name for the new folder (e.g. 'Q3 Newsletters').

Returns: JSON with id (new folder ID), name, and count of campaigns in the folder.

Inputs: name (required), account. Returns: result

create_connected_siteA

Connect a website to Mailchimp, generating a tracking script for that domain.

Use to enable site tracking and pop-up forms on a domain you control. After creation, install the returned script, then call verify_connected_site_script to confirm installation. Use list_connected_sites to check existing sites first.

Args: foreign_id: A unique identifier of your choosing for this site (e.g. 'my-store'). domain: The website domain to connect (e.g. 'www.example.com').

Returns: JSON with id, foreign_id, domain, site_script (object with url and fragment), status, created_at, updated_at.

Inputs: domain (required), foreign_id (required), account. Returns: result

create_interestA

Create a new interest option within an interest category (e.g. add "Tech" to a "Topics" category).

Use after create_interest_category to add selectable options. Each option becomes available on signup forms (unless category type is 'hidden'). Use list_interests to check existing options. Use delete_interest to remove an option.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. category_id: The interest category ID. Obtain from list_interest_categories or create_interest_category. name: Display name for the interest option (e.g. 'Tech', 'Sports'). Must be unique within the category.

Returns: JSON with fields: id (string, use with delete_interest), name, subscriber_count (int, starts at 0).

Example: create_interest(list_id="abc123", category_id="cat456", name="Technology") -> {"id": "int789", "name": "Technology", "subscriber_count": 0}

Inputs: name (required), list_id (required), category_id (required), account. Returns: result

create_interest_categoryA

Create a new interest category (group container) in an audience for organizing subscriber preferences.

Use to create a container for interest options. Typical workflow: create_interest_category -> create_interest (add options within the category). The type controls how subscribers interact with it on signup forms. Use list_interest_categories to check existing categories first.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. title: Display title for the category (e.g. 'Preferred Topics'). Must be unique within the audience. type: How the category appears on signup forms. Valid values: 'checkboxes' (subscribers can select multiple), 'dropdown' (single select), 'radio' (single select), 'hidden' (not shown on forms, managed via API only).

Returns: JSON with fields: id (string, use with create_interest, list_interests, delete_interest_category), title, type, list_id.

Example: create_interest_category(list_id="abc123", title="Newsletter Preferences", type="checkboxes") -> {"id": "cat456", "title": "Newsletter Preferences", "type": "checkboxes", ...}

Inputs: type (required), title (required), list_id (required), account. Returns: result

create_landing_pageA

Create a new landing page in draft status from a template, optionally linked to a store.

The page is created unpublished. Use update_landing_page to edit settings or publish_landing_page to make it live at its public URL. Use list_landing_pages or get_landing_page to inspect existing pages.

Returns 400 error if template_id is invalid or list_id does not exist.

Args: name: Internal name for the page (shown in the Mailchimp dashboard, not to visitors). title: Browser tab title (shown in the page's HTML ). list_id: Audience ID this page collects signups for (e.g. 'abc123def4'). Obtain from list_audiences. template_id: Template ID to base the page on. Obtain from list_templates. store_id: Optional e-commerce store ID to link the page to. Obtain from list_ecommerce_stores. description: Optional internal description. tracking_opens: Track view-opens analytics. Default true. tracking_clicks: Track link clicks analytics. Default true.

Returns: JSON with id (use as page_id for subsequent calls), name, title, status ('unpublished'), url (null until published), created_at, list_id.

Inputs: name (required), title (required), list_id (required), template_id (required), +5 more. Returns: result

create_merge_fieldA

Create a new custom merge field in an audience for storing additional member data.

Use to add custom data fields beyond the defaults (FNAME, LNAME, ADDRESS, PHONE). Once created, populate per-member via add_member/update_member using the tag name. The type cannot be changed after creation. Use list_merge_fields to check existing fields first.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. name: Display name for the field (e.g. 'Company Name'). type: Field data type. Valid values: 'text', 'number', 'address', 'date', 'birthday', 'phone', 'url', 'imageurl', 'zip', 'dropdown', 'radio'. Cannot be changed after creation. tag: Short uppercase tag name (e.g. 'COMPANY'). Max 10 characters, letters and numbers only. Auto-generated from name if omitted. Used as |TAG| in email content. required: Whether the field is required when subscribing (default false). default_value: Default value for new subscribers. choices: Comma-separated choices for 'dropdown' or 'radio' types (e.g. 'Small,Medium,Large'). Required when type is 'dropdown' or 'radio'. Ignored for other types.

Returns: JSON with fields: merge_id (int, for update/delete), tag (string), name, type, required.

Example: create_merge_field(list_id="abc123", name="Company", type="text", tag="COMPANY") -> {"merge_id": 5, "tag": "COMPANY", "name": "Company", "type": "text", ...}

Inputs: name (required), type (required), list_id (required), tag, +4 more. Returns: result

create_promo_codeA

Create a redeemable code under an existing promo rule.

Customers type the code string at checkout to apply the rule's discount. Code matching is case-insensitive on the Mailchimp side. Use list_promo_codes to discover existing codes before creating duplicates.

Returns 400 if promo_rule_id does not exist; returns 409 if promo_code_id already exists.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID to attach the code to. Obtain from list_promo_rules. promo_code_id: Client-supplied unique ID for the code. code: The actual code string customers type at checkout (e.g. 'SUMMER20'). redemption_url: URL where the code can be applied (your checkout page). enabled: Whether the code is active. Default true.

Returns: JSON with id, code, redemption_url, usage_count (0 at creation), enabled, created_at.

Inputs: code (required), store_id (required), promo_code_id (required), promo_rule_id (required), +3 more. Returns: result

create_promo_ruleA

Create a promo rule (discount mechanic) in a store. Attach codes to it afterwards via create_promo_code.

promo_rule_id is client-supplied. Common patterns: amount=20 + type='percentage' + target='total' for '20% off entire order'; amount=5 + type='fixed' + target='shipping' for '$5 off shipping'.

Args: store_id: E-commerce store ID. promo_rule_id: Client-supplied unique ID for the rule. description: Internal description shown in Mailchimp UI. amount: Discount value. For type='percentage', a value between 0 and 100. type: 'fixed' for absolute amount or 'percentage' for percent off. target: 'per_item' (each item), 'total' (whole order), or 'shipping' (shipping cost only). enabled: Whether the rule is active. Default true. title: Optional public title. starts_at: Optional ISO 8601 start datetime (rule inactive before this). ends_at: Optional ISO 8601 end datetime (rule inactive after this).

Returns: JSON with id, title, description, amount, type, target, enabled, created_at.

Inputs: type (required), amount (required), target (required), store_id (required), +7 more. Returns: result

create_segmentA

Create a new segment or tag in an audience for grouping members.

Static segments (default) have manual membership via add_members_to_segment. Dynamic segments auto-update based on filter conditions. No destructive side effects. Use tag_member to apply tags to individual members instead.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. name: Display name for the segment or tag. static: True (default) for manual membership; false for dynamic (requires match + conditions_json). match: Condition logic for dynamic segments: 'all' (AND) or 'any' (OR). Required when static=false. conditions_json: JSON conditions array for dynamic segments. Required when static=false.

Returns: JSON with id (new segment ID), name, member_count, type ('static'/'saved'), options.

Inputs: name (required), list_id (required), match, static, +2 more. Returns: result

create_storeA

Create an e-commerce store in Mailchimp to hold products, customers, carts, and orders.

A store is the top-level container that connects purchase data to an audience for segmentation and product recommendations. Many stores sync automatically via Shopify or WooCommerce integrations; these manual writes suit custom or headless storefronts.

Args: store_id: Client-supplied unique ID for the new store (e.g. 'store_1'). name: Human-readable store name shown in the Mailchimp UI. currency_code: ISO 4217 currency code (e.g. 'USD', 'EUR'). additional_fields: Optional dict of extra documented fields (e.g. list_id, domain, email_address, primary_locale, timezone) merged into the request body.

Returns: JSON with the created store object.

Inputs: name (required), store_id (required), currency_code (required), account, +1 more. Returns: result

create_store_cartA

Create a cart in a store with line items and a customer reference. Used to push abandoned-cart data from an external system into Mailchimp for recovery workflows.

cart_id is client-supplied (Mailchimp does not auto-generate it). The customer must already exist in the store; create them via Mailchimp's customer endpoints first if not. Use update_store_cart to modify after creation.

Args: store_id: E-commerce store ID. cart_id: Client-supplied unique ID for the new cart (e.g. 'cart_42'). customer_id: ID of an existing customer in the store. currency_code: ISO 4217 currency code (e.g. 'USD', 'EUR'). order_total: Total order amount (line items + tax + shipping if any). lines_json: JSON string with the cart line items array. Example: '[{"id": "line_1", "product_id": "p_1", "product_variant_id": "p_1_red", "quantity": 2, "price": 19.99}]' checkout_url: Optional URL to resume the cart (used in recovery emails). tax_total: Optional tax portion of order_total.

Returns: JSON with id, customer, currency_code, order_total, checkout_url, created_at.

Inputs: cart_id (required), store_id (required), lines_json (required), customer_id (required), +5 more. Returns: result

create_store_customerA

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.

Inputs: store_id (required), customer_id (required), email_address (required), opt_in_status (required), +2 more. Returns: result

create_store_orderA

Create an e-commerce order in a store with a customer and line items.

order_id is client-supplied and must be unique within the store; the customer must already exist or be provided inline with the required id. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync orders automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Client-supplied unique ID for the new order (e.g. 'order_42'). customer: Customer object dict. Must include 'id'; may include email_address, opt_in_status, first_name, last_name. lines: List of order line dicts. Each requires id, product_id, product_variant_id, quantity, price. additional_fields: Optional dict of extra order fields merged into the body (e.g. currency_code, order_total, financial_status, processed_at_foreign, promos).

Returns: JSON with the created order object.

Inputs: lines (required), customer (required), order_id (required), store_id (required), +2 more. Returns: result

create_store_order_lineA

Add a line item to an existing e-commerce order.

line_id is client-supplied and must be unique within the order; product_id and product_variant_id must reference products that already exist in the store. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync order lines automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID to add the line to. line_id: Client-supplied unique ID for the new line (e.g. 'line_1'). product_id: ID of an existing product in the store. product_variant_id: ID of an existing variant of that product. quantity: Quantity ordered. price: Unit price of the line item. additional_fields: Optional dict of extra line fields merged into the body (e.g. discount).

Returns: JSON with the created line object.

Inputs: price (required), line_id (required), order_id (required), quantity (required), +5 more. Returns: result

create_store_productA

Create a product in a store, including at least one variant.

Every product needs one or more variants; a simple product still has a single default variant. Many stores sync products automatically via Shopify or WooCommerce integrations; these manual writes suit custom or headless storefronts.

Args: store_id: E-commerce store ID. product_id: Client-supplied unique ID for the new product. title: Product title shown in emails and the Mailchimp UI. variants: List of variant dicts (minimum 1), each with at least an id and title (e.g. [{"id": "v1", "title": "Default", "price": 19.99}]). additional_fields: Optional dict of extra documented fields (e.g. handle, url, description, type, vendor, image_url, images) merged into the request body.

Returns: JSON with the created product object.

Inputs: title (required), store_id (required), variants (required), product_id (required), +2 more. Returns: result

create_store_product_imageA

Add an image to a product in an e-commerce store.

image_id is client-supplied and must be unique within the product; url must point to a publicly reachable image. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID to attach the image to. image_id: Client-supplied unique ID for the new image (e.g. 'img_1'). url: Publicly reachable URL of the image. additional_fields: Optional dict of extra image fields merged into the body (e.g. variant_ids).

Returns: JSON with the created image object.

Inputs: url (required), image_id (required), store_id (required), product_id (required), +2 more. Returns: result

create_store_product_variantA

Add a new variant to an existing product in a store.

Use to represent a distinct SKU, size, or color of a product. Many stores sync variants automatically via Shopify or WooCommerce integrations; these manual writes suit custom or headless storefronts.

Args: store_id: E-commerce store ID. product_id: Product ID to add the variant to. variant_id: Client-supplied unique ID for the new variant. title: Variant title (e.g. 'Large / Blue'). additional_fields: Optional dict of extra documented fields (e.g. url, sku, price, inventory_quantity, image_url) merged into the request body.

Returns: JSON with the created variant object.

Inputs: title (required), store_id (required), product_id (required), variant_id (required), +2 more. Returns: result

create_templateA

Create a new reusable email template from HTML content.

Use to save HTML email designs for reuse across campaigns. Retrieve template HTML later via get_template_default_content for use with set_campaign_content. Use list_templates to browse existing templates. Do not use for one-off emails; use set_campaign_content directly instead.

Args: name: Display name for the template (e.g. 'Monthly Newsletter v2'). html: Complete HTML content. Must be valid HTML with inline CSS for email client compatibility. Mailchimp merge tags (e.g. |FNAME|, |UNSUB|) are supported. folder_id: Optional template folder ID to organize the template. Obtain from the Mailchimp web UI.

Returns: JSON with id (int, new template ID), name, type ('user'), active (boolean), date_created.

Inputs: html (required), name (required), account, folder_id. Returns: result

create_template_folderA

Create a new folder to organize templates.

Use to group related templates for easier navigation. Assign templates to the folder via the folder_id field when creating them. Use list_template_folders to browse existing folders.

Args: name: Display name for the new folder (e.g. 'Promotional Templates').

Returns: JSON with id (new folder ID), name, and count of templates in the folder.

Inputs: name (required), account. Returns: result

create_verified_domainA

Begin domain verification by sending a verification code to an address at that domain.

The domain is derived from the part of verification_email after the '@'. Mailchimp emails a code to this address; pass it to verify_verified_domain to complete verification. Use list_verified_domains to check existing domains before starting.

Args: verification_email: A mailbox at the domain to verify (e.g. 'admin@mail.example.com'). The verification code is sent here.

Returns: JSON with domain, verified (boolean), authenticated (boolean), verification_status, authentication_status.

Inputs: verification_email (required), account. Returns: result

create_webhookA

Create a webhook that sends HTTP POST notifications to an external URL on audience events.

Side effect: Mailchimp sends a validation GET request during creation; the URL must be publicly accessible and return HTTP 200. All events and sources enabled by default if omitted. Do not use for polling or batch data retrieval; use list_audience_members or campaign reports instead.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. url: Public HTTPS URL to receive POST requests. Must return HTTP 200 on GET validation. events: Comma-separated events: 'subscribe', 'unsubscribe', 'profile', 'cleaned', 'upemail', 'campaign'. All enabled if omitted. sources: Comma-separated sources: 'user', 'admin', 'api'. All enabled if omitted.

Returns: JSON with id, url, events (boolean flags), sources (boolean flags). Error if URL validation fails.

Inputs: url (required), list_id (required), events, account, +1 more. Returns: result

customize_signup_formA

Customize an audience's default signup form (header, content sections, and styles).

At least one of header, contents, or styles must be provided. Use list_signup_forms first to inspect the current form and mirror its structure.

Args: list_id: Audience/list ID (from list_audiences). header: Optional header object, e.g. {"image_url": "...", "text": "...", "background_color": "..."}. contents: Optional array of content sections, each {"section": , "value": }. Section names include 'signup_message', 'unsub_message', 'signup_thank_you_title'. styles: Optional array of style sections, each {"section": , "options": [{"property": , "value": }]}.

Returns: JSON with the updated signup form configuration, or an error object.

Inputs: list_id (required), header, styles, account, +1 more. Returns: result

delete_audienceA
DestructiveIdempotent

Permanently delete an audience and all its members, segments, campaigns, and stats. Irreversible.

Side effect: removes every member of the audience and all historical data tied to it. Cannot be undone via the API. Use update_audience to rename or archive-like changes instead. Use list_audience_members to back up members first if needed.

Returns 404 error if list_id does not exist.

Args: list_id: Audience/list ID to delete (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. Double-check before calling — deletion is permanent.

Returns: JSON with status ('deleted') and list_id on success, or error object on failure.

Inputs: list_id (required), account. Returns: result

delete_batch_webhookA
DestructiveIdempotent

Delete a batch webhook permanently.

Irreversible. Mailchimp will stop sending batch-completion callbacks to the webhook's URL. Use list_batch_webhooks to find batch_webhook_id values.

Returns 404 error if batch_webhook_id is invalid.

Args: batch_webhook_id: The batch webhook ID to delete. Obtain from list_batch_webhooks.

Returns: JSON confirming the deletion, or an error object if batch_webhook_id is invalid. On success the Mailchimp API returns an empty body (HTTP 204).

Inputs: batch_webhook_id (required), account. Returns: result

delete_campaignA
DestructiveIdempotent

Permanently delete a campaign from the account.

Use to remove unwanted draft or scheduled campaigns. Only works on campaigns that have not been sent (status 'save' or 'schedule'). Sent campaigns cannot be deleted and will return an error. Use replicate_campaign to clone before deleting if you want to preserve settings.

Args: campaign_id: The campaign ID to delete (e.g. 'abc123def4'). Must not be a sent campaign.

Returns: JSON with fields: status ("deleted"), campaign_id. Returns error if the campaign has already been sent.

Example: delete_campaign(campaign_id="abc123") -> {"status": "deleted", "campaign_id": "abc123"}

Inputs: campaign_id (required), account. Returns: result

delete_campaign_feedbackA
DestructiveIdempotent

Delete a campaign feedback comment permanently.

Irreversible. Use to remove an obsolete collaboration note. Use list_campaign_feedback to discover feedback IDs.

Args: campaign_id: Campaign ID the feedback belongs to. Obtain from list_campaigns. feedback_id: Feedback comment ID to delete. Obtain from list_campaign_feedback.

Returns: JSON with status ("deleted"), campaign_id, feedback_id.

Inputs: campaign_id (required), feedback_id (required), account. Returns: result

delete_campaign_folderA
DestructiveIdempotent

Delete a campaign folder permanently.

Irreversible. Deleting a folder does not delete the campaigns inside it; they become unfiled. Use list_campaign_folders to discover folder IDs.

Args: folder_id: Campaign folder ID to delete. Obtain from list_campaign_folders.

Returns: JSON with status ("deleted") and folder_id.

Inputs: folder_id (required), account. Returns: result

delete_connected_siteA
DestructiveIdempotent

Delete a connected site from the account permanently.

Irreversible. After deletion, tracking and pop-up forms tied to this site stop working. Use list_connected_sites to find connected site IDs first.

Args: connected_site_id: The connected site ID to delete. Obtain from list_connected_sites.

Returns: JSON with status ("deleted"), connected_site_id.

Inputs: connected_site_id (required), account. Returns: result

delete_fileA
DestructiveIdempotent

Permanently delete a file from the File Manager.

Irreversible. Any campaign or template still referencing the file's hosted URL will show a broken image afterwards. Use list_files to find the file_id and get_file to confirm the target before deleting.

Args: file_id: File ID (numeric, as a string) from list_files.

Returns: JSON with status 'success' on deletion, or an error object if file_id is invalid.

Inputs: file_id (required), account. Returns: result

delete_interestA
DestructiveIdempotent

Delete a single interest option from a category, keeping the category and other options intact.

Use to remove one specific option. The interest and its subscriber associations are removed. Use delete_interest_category instead to remove the entire category with all options at once.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. category_id: The interest category ID. Obtain from list_interest_categories. interest_id: The interest option ID to delete. Obtain from list_interests.

Returns: JSON with fields: status ("deleted"), interest_id. Returns error if interest does not exist.

Example: delete_interest(list_id="abc123", category_id="cat456", interest_id="int789") -> {"status": "deleted", "interest_id": "int789"}

Inputs: list_id (required), category_id (required), interest_id (required), account. Returns: result

delete_interest_categoryA
DestructiveIdempotent

Delete an interest category and all its interest options at once.

Removes the entire category with all its options. All subscriber associations with interests in this category are removed. Subscribers themselves are not affected. Use delete_interest instead to remove a single option while keeping the category. Use list_interest_categories to find category IDs.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. category_id: The interest category ID to delete. Obtain from list_interest_categories.

Returns: JSON with fields: status ("deleted"), category_id. Returns error if category does not exist.

Example: delete_interest_category(list_id="abc123", category_id="cat456") -> {"status": "deleted", "category_id": "cat456"}

Inputs: list_id (required), category_id (required), account. Returns: result

delete_landing_pageA
DestructiveIdempotent

Permanently delete a landing page. Cannot be undone.

Side effect: the page becomes inaccessible at its public URL immediately. Past visit analytics remain in Mailchimp's reports area but the page itself is gone. Use unpublish_landing_page if you only want to take it offline temporarily.

Returns 404 error if page_id is invalid.

Args: page_id: Landing page ID to delete. Obtain from list_landing_pages.

Returns: JSON with status ('deleted') and page_id on success.

Inputs: page_id (required), account. Returns: result

delete_memberA
DestructiveIdempotent

Permanently delete a member and all their data from an audience.

Use only for complete data removal (e.g. GDPR right-to-erasure requests). All activity history, merge field data, and tag associations are permanently lost. Equivalent to delete_member_permanent (same endpoint). Use unsubscribe_member instead to stop sending while preserving data for reporting. There is no undo.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email address of the member to permanently delete. Must exist in the audience.

Returns: JSON with fields: status ("permanently_deleted"), email_address. Returns error if the member does not exist.

Example: delete_member(list_id="abc123", email_address="jane@co.com") -> {"status": "permanently_deleted", "email_address": "jane@co.com"}

Inputs: list_id (required), email_address (required), account. Returns: result

delete_member_noteA
DestructiveIdempotent

Permanently delete a note attached to a member. Cannot be undone.

Use list_member_notes to find note_ids before calling. Does not affect the member itself, only the note.

Returns 404 if the note or member does not exist.

Args: list_id: Audience/list ID. Obtain from list_audiences. email_address: Email of the member who owns the note. note_id: Note ID to delete. Obtain from list_member_notes.

Returns: JSON with status ('deleted'), email_address, note_id on success.

Inputs: list_id (required), note_id (required), email_address (required), account. Returns: result

delete_member_permanentA
DestructiveIdempotent

Permanently and irreversibly erase an audience member (GDPR-style deletion).

IRREVERSIBLE: this permanently deletes all personal data for the member and prevents that email from ever being re-imported into the audience. This tool and delete_member are equivalent: both call the same permanent-deletion endpoint. To merely stop sending while keeping the member for reporting, use unsubscribe_member instead.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: The member's email address. The subscriber hash is derived automatically.

Returns: JSON confirming the permanent deletion, or an error object if the member is not found. On success the Mailchimp API returns an empty body (HTTP 204).

Inputs: list_id (required), email_address (required), account. Returns: result

delete_merge_fieldA
DestructiveIdempotent

Delete a custom merge field and all its stored data from an audience.

Use only when you no longer need the field. All data stored in this field for every member is permanently lost. Default fields (FNAME, LNAME, ADDRESS, PHONE) cannot be deleted and will return an error. Use list_merge_fields to find merge_id values.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. merge_id: The merge field ID to delete (numeric string). Obtain from list_merge_fields. Cannot be a default field.

Returns: JSON with fields: status ("deleted"), merge_id. Returns error if the field is a default field or does not exist.

Example: delete_merge_field(list_id="abc123", merge_id="5") -> {"status": "deleted", "merge_id": "5"}

Inputs: list_id (required), merge_id (required), account. Returns: result

delete_promo_codeA
DestructiveIdempotent

Permanently delete a promo code. Past redemption history is lost. Irreversible.

Use update_promo_code with enabled=false to disable a code while preserving its redemption stats. Use delete_promo_rule to remove the rule and all its codes at once.

Returns 404 if any of store_id, promo_rule_id, or promo_code_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID the code is attached to. promo_code_id: Code ID to delete.

Returns: JSON with status ('deleted'), store_id, promo_rule_id, promo_code_id on success.

Inputs: store_id (required), promo_code_id (required), promo_rule_id (required), account. Returns: result

delete_promo_ruleA
DestructiveIdempotent

Permanently delete a promo rule and all its associated promo codes. Irreversible.

Side effect: every promo code attached to this rule is also deleted and stops working at checkout. Use update_promo_rule with enabled=false to disable a rule without deleting its codes.

Returns 404 if store_id or promo_rule_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID to delete.

Returns: JSON with status ('deleted'), store_id, promo_rule_id on success.

Inputs: store_id (required), promo_rule_id (required), account. Returns: result

delete_segmentA
DestructiveIdempotent

Delete a segment or tag from an audience. Members remain in the audience.

Irreversible. Use update_segment to rename or modify conditions instead of deleting. Use list_segments to find segment IDs.

Returns 404 error if segment does not exist.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. segment_id: Segment/tag ID to delete (numeric string, e.g. '12345'). Obtain from list_segments.

Returns: JSON with status ("deleted"), segment_id.

Inputs: list_id (required), segment_id (required), account. Returns: result

delete_storeA
DestructiveIdempotent

Permanently delete an e-commerce store from Mailchimp.

This is a destructive cascade: deleting a store also removes all of its products, variants, customers, carts, and orders, and cannot be undone. Verify the store_id carefully before calling.

Args: store_id: E-commerce store ID to delete.

Returns: JSON confirming deletion (empty body on success).

Inputs: store_id (required), account. Returns: result

delete_store_cartA
DestructiveIdempotent

Permanently delete a cart from a store. Cannot be undone.

Use when an external system reports the cart has been completed (converted to order) or expired. Does not affect related orders or customer records.

Returns 404 if store_id or cart_id is invalid.

Args: store_id: E-commerce store ID. cart_id: Cart ID to delete.

Returns: JSON with status ('deleted'), store_id, cart_id on success.

Inputs: cart_id (required), store_id (required), account. Returns: result

delete_store_customerA
DestructiveIdempotent

Permanently delete a customer from a store.

This cannot be undone and removes the customer's link to their store purchase data. It does not remove them from the connected audience.

Args: store_id: E-commerce store ID. customer_id: Customer ID to delete.

Returns: JSON confirming deletion (empty body on success).

Inputs: store_id (required), customer_id (required), account. Returns: result

delete_store_orderA
DestructiveIdempotent

Permanently delete an e-commerce order from a store.

This removes the order and its lines and cannot be undone. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync orders automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID to delete.

Returns: JSON confirming deletion (empty body on success) or an error object.

Inputs: order_id (required), store_id (required), account. Returns: result

delete_store_order_lineA
DestructiveIdempotent

Permanently delete a line item from an e-commerce order.

This removes the line from the order and cannot be undone. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync order lines automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID that owns the line. line_id: Line item ID to delete.

Returns: JSON confirming deletion (empty body on success) or an error object.

Inputs: line_id (required), order_id (required), store_id (required), account. Returns: result

delete_store_productA
DestructiveIdempotent

Permanently delete a product and all of its variants from a store.

This cannot be undone and also removes the product's variants. Verify the product_id before calling.

Args: store_id: E-commerce store ID. product_id: Product ID to delete.

Returns: JSON confirming deletion (empty body on success).

Inputs: store_id (required), product_id (required), account. Returns: result

delete_store_product_imageA
DestructiveIdempotent

Permanently delete an image from a product in an e-commerce store.

This removes the image and cannot be undone. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID that owns the image. image_id: Image ID to delete.

Returns: JSON confirming deletion (empty body on success) or an error object.

Inputs: image_id (required), store_id (required), product_id (required), account. Returns: result

delete_store_product_variantA
DestructiveIdempotent

Permanently delete a single variant from a product in a store.

This cannot be undone. A product must retain at least one variant, so deleting its last variant may be rejected by the API.

Args: store_id: E-commerce store ID. product_id: Product ID that owns the variant. variant_id: Variant ID to delete.

Returns: JSON confirming deletion (empty body on success).

Inputs: store_id (required), product_id (required), variant_id (required), account. Returns: result

delete_templateA
DestructiveIdempotent

Delete a user-created template permanently.

Irreversible. Only works for user-created templates; gallery and base templates cannot be deleted. Does not affect campaigns already using this template's content. Use list_templates to find template IDs.

Returns 404 error if template_id is invalid or is not a user template.

Args: template_id: Template ID to delete (numeric string, e.g. '12345'). Must be type 'user'.

Returns: JSON with status ("deleted"), template_id.

Inputs: template_id (required), account. Returns: result

delete_template_folderA
DestructiveIdempotent

Delete a template folder permanently.

Irreversible. Deleting a folder does not delete the templates inside it; they become unfiled. Use list_template_folders to discover folder IDs.

Args: folder_id: Template folder ID to delete. Obtain from list_template_folders.

Returns: JSON with status ("deleted") and folder_id.

Inputs: folder_id (required), account. Returns: result

delete_verified_domainA
DestructiveIdempotent

Delete a verified sending domain from the account permanently.

Irreversible. After deletion the domain can no longer be used as a sending address until re-verified. Use list_verified_domains to find domain names first.

Args: domain_name: The sending domain to delete (e.g. 'mail.example.com'). Obtain from list_verified_domains.

Returns: JSON with status ("deleted"), domain_name.

Inputs: domain_name (required), account. Returns: result

delete_webhookA
DestructiveIdempotent

Delete a webhook, immediately stopping event notifications to its URL.

Irreversible. Do not use when you want to temporarily pause notifications; webhooks have no pause mechanism. Use create_webhook to set up a replacement afterward.

Returns 404 error if webhook_id or list_id is invalid.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. webhook_id: The webhook ID to delete. Obtain from list_webhooks.

Returns: JSON with status ("deleted"), webhook_id.

Inputs: list_id (required), webhook_id (required), account. Returns: result

describe_toolsA
Read-only

List every tool with its machine-readable risk classification for policy enforcement.

Use this to discover which tools are reads, reversible writes, or destructive (irreversible) before granting access or building automation. A runtime-security gateway can also read the same signal from the MCP tool annotations (readOnlyHint / destructiveHint / idempotentHint) exposed via tools/list; this tool is the convenience, tool-call-based view of that metadata.

No network call. Read-only, safe to retry.

Returns: JSON with summary (counts per risk tier and destructive total) and tools array. Each: name, risk ('read' | 'write' | 'destructive'), read_only (bool), destructive (bool), idempotent (bool).

Inputs: no named parameters. Returns: result

get_account_exportA
Read-only

Retrieve the status and download URL for a single account export job.

Use to poll an export until its status is finished and then read its download_url. Use list_account_exports to browse all exports and discover IDs instead.

Args: export_id: The export job ID to inspect. Obtain from list_account_exports or create_account_export.

Returns: JSON with export_id, status, started (ISO 8601), finished (ISO 8601 or null), size_in_bytes, download_url.

Inputs: export_id (required), account. Returns: result

get_account_infoA
Read-only

Retrieve Mailchimp account details including name, contact info, total subscribers, and industry benchmarks.

Use this to verify API connectivity or inspect account-level metrics. Typically the first call in a workflow. Do not use this as a health check; use ping instead (faster, no payload). Use list_audiences to get per-audience stats.

Returns: JSON with fields: account_name (string), email (account owner), first_name, last_name, total_subscribers (int, all audiences combined), industry_stats (object with open/click rate benchmarks for the account's industry). Returns an error object if the API key is invalid or missing.

Example: get_account_info() -> {"account_name": "My Company", "total_subscribers": 5000, "industry_stats": {"open_rate": 0.21, ...}}

Inputs: account. Returns: result

get_audience_abuse_reportA
Read-only

Retrieve the details of a single abuse (spam) complaint report for an audience.

Use to inspect which member and campaign a specific complaint relates to. Use list_audience_abuse_reports to browse all reports and discover report_id values.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. report_id: The abuse report ID. Obtain from list_audience_abuse_reports.

Returns: JSON with id, campaign_id, list_id, email_id, email_address, merge_fields, vip (boolean), date (ISO 8601). Returns error if list_id or report_id is invalid.

Inputs: list_id (required), report_id (required), account. Returns: result

get_audience_activityA
Read-only

Retrieve the recent daily activity (opens, clicks, sends, subscribes) for an audience.

Use to inspect an audience's day-by-day engagement history over its recent lifetime. Use get_audience_details for aggregate stats and list_campaigns for per-campaign performance.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. count: Number of daily activity records to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and activity array. Each record: day (date), emails_sent, unique_opens, recipient_clicks, hard_bounce, soft_bounce, subs, unsubs, other_adds, other_removes.

Inputs: list_id (required), count, offset, account. Returns: result

get_audience_clientsA
Read-only

List the top email clients (Gmail, Apple Mail, Outlook) used by an audience's members.

Use to inform email rendering and design decisions based on which clients dominate an audience. Use get_audience_top_locations for geographic distribution instead.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. count: Number of email clients to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and clients array. Each: client (email client name) and members (number of audience members using that client).

Inputs: list_id (required), count, offset, account. Returns: result

get_audience_detailsA
Read-only

Retrieve full stats, subscribe URL, and rating for a specific audience.

Use when you have a list_id and need detailed metrics or the public subscribe URL. Use list_audiences to browse all audiences and discover list_ids instead.

Returns 404 error if list_id is invalid.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences.

Returns: JSON with id, name, stats (member_count, unsubscribe_count, open_rate, click_rate), date_created, list_rating (0-5), subscribe_url_short, and audience settings: campaign_defaults (from_name, from_email, subject, language), double_optin (bool: true = confirmed/double opt-in), marketing_permissions (bool: GDPR permission fields enabled), email_type_option (bool).

Inputs: list_id (required), account. Returns: result

get_audience_growth_historyA
Read-only

Retrieve monthly growth history for an audience (subscribes, unsubscribes, cleaned).

Each record is one calendar month, ordered newest first. Use get_audience_details for current totals instead of historical trends.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. count: Months to return (1-1000, default 12).

Returns: JSON with list_id and history array. Each: month (YYYY-MM), subscribed, unsubscribed, reconfirm, cleaned, pending, transactional (all cumulative ints).

Inputs: list_id (required), count, account. Returns: result

get_audience_top_locationsA
Read-only

List the top geographic locations (countries) of an audience's members.

Use to understand where an audience is based for regional targeting or reporting. Use get_campaign_locations for the geographic breakdown of a single campaign's opens instead.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. count: Number of locations to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and locations array. Each: country, cc (2-char country code), percent (share of the audience), total (member count in that country).

Inputs: list_id (required), count, offset, account. Returns: result

get_authorized_appA
Read-only

Retrieve the full record for a single OAuth-authorized application.

Use when you have an app ID and need its name, description, or the users that authorized it. Use list_authorized_apps to browse all apps and discover IDs instead.

Args: app_id: The authorized app ID to inspect. Obtain from list_authorized_apps.

Returns: JSON with id, name, description, users (array of account usernames that authorized it).

Inputs: app_id (required), account. Returns: result

get_automation_emailA
Read-only

Get details of a single email in a classic automation workflow.

Retrieves the configuration and status of one automation email identified by its workflow and email IDs. Use this to inspect a specific step before pausing, starting, or queueing subscribers.

Args: workflow_id: The unique id of the classic automation workflow. workflow_email_id: The unique id of the automation email within the workflow.

Returns: JSON with the automation email details.

Inputs: workflow_id (required), workflow_email_id (required), account. Returns: result

get_automation_email_queueA
Read-only

Retrieve the queue of subscribers about to receive a specific automation email, with scheduled send times.

Use to see who is waiting to receive a particular email in a workflow. Use get_automation_emails first to find email_id values within the workflow.

Args: automation_id: The automation workflow ID (e.g. 'auto123'). Obtain from list_automations. email_id: The specific email ID within the automation. Obtain from get_automation_emails.

Returns: JSON with total_items (int) and queue array. Each entry: email_address (string), next_send (ISO 8601 timestamp of scheduled send).

Example: get_automation_email_queue(automation_id="auto123", email_id="email456") -> {"total_items": 12, "queue": [{"email_address": "jane@co.com", "next_send": "2025-06-02T10:00:00Z"}]}

Inputs: email_id (required), automation_id (required), account. Returns: result

get_automation_emailsA
Read-only

List individual emails within an automation workflow with sequence, delays, and send counts.

Returns all emails regardless of status. Do not confuse with get_email_activity (campaign engagement). Use get_automation_email_queue to see queued subscribers for a specific email.

Args: automation_id: Automation workflow ID (e.g. 'auto123'). Obtain from list_automations.

Returns: JSON with total_items and emails array. Each email: id, position (sequence starting at 1), status ('sending'/'paused'/'draft'), subject_line, title, emails_sent, send_time, delay.

Inputs: automation_id (required), account. Returns: result

get_automation_queue_subscriberA
Read-only

Get a single subscriber from the queue of a classic automation email.

Retrieves the queue status for a specific subscriber within an automation email. The subscriber is located by hashing the provided email address.

Args: workflow_id: The unique id of the classic automation workflow. workflow_email_id: The unique id of the automation email whose queue to inspect. email_address: The email address of the queued subscriber to look up.

Returns: JSON with the queued subscriber details.

Inputs: workflow_id (required), email_address (required), workflow_email_id (required), account. Returns: result

get_automation_removed_subscriberA
Read-only

Get a single subscriber removed from a classic automation workflow.

Retrieves details for a specific subscriber that was removed from the automation workflow. The subscriber is located by hashing the provided email address.

Args: workflow_id: The unique id of the classic automation workflow. email_address: The email address of the removed subscriber to look up.

Returns: JSON with the removed subscriber details.

Inputs: workflow_id (required), email_address (required), account. Returns: result

get_automation_summaryA
Read-only

Summarise automation activity across Classic Automations and Customer Journeys.

Combines two API calls into a single overview useful for audits and dashboards:

  1. /automations to count Classic workflows by status (sending / paused / draft)

  2. /campaigns?type=automation&since_send_time=N days ago to count and sum what automations have actually sent recently (both Classic and Customer Journey emails show up as type='automation' campaigns)

This is the recommended starting point for "what's my automation stack doing right now?" questions during an account audit. Use list_automations for the raw Classic list. Use search_automation_campaigns for the raw recent automation campaign feed.

Read-only, safe to retry.

Args: days: Lookback window in days for the recent-sends portion (1-365, default 30).

Returns: JSON with two sections: - classic_automations: total, by_status ({sending, paused, draft, ...}) - recent_automation_campaigns: window_days, total_campaigns, total_emails_sent, top_titles (up to 5 titles ordered by emails_sent desc)

Inputs: days, account. Returns: result

get_batch_statusA
Read-only

Check the progress and completion status of an asynchronous batch operation.

Use after create_batch to poll for completion. Call repeatedly until status is 'finished'. Do not use for non-batch operations. Use list_batches to see all recent batch operations.

Args: batch_id: The batch operation ID (e.g. 'batch123abc'). Obtain from create_batch.

Returns: JSON with fields: id, status ('pending' = queued, 'started' = in progress, 'finished' = complete), total_operations (int), finished_operations (int), errored_operations (int), submitted_at (ISO 8601), completed_at (ISO 8601 or null), response_body_url (string, downloadable tar.gz archive with per-operation results, only available when status is 'finished').

Example: get_batch_status(batch_id="batch123") -> {"status": "finished", "total_operations": 100, "finished_operations": 100, "errored_operations": 2, "response_body_url": "https://...", ...}

Inputs: batch_id (required), account. Returns: result

get_batch_webhookA
Read-only

Retrieve the details of a single batch webhook.

Use to inspect a batch webhook's target URL and enabled state. Use list_batch_webhooks to browse all batch webhooks and discover batch_webhook_id values.

Args: batch_webhook_id: The batch webhook ID. Obtain from list_batch_webhooks.

Returns: JSON with id, url, enabled (boolean). Returns error if batch_webhook_id is invalid.

Inputs: batch_webhook_id (required), account. Returns: result

get_campaign_abuse_reportA
Read-only

Retrieve a single abuse (spam) complaint for a sent campaign.

Use to inspect the details of one complaint, including which member filed it and when. Use get_campaign_abuse_reports to discover report IDs.

Args: campaign_id: Sent campaign ID. Obtain from list_campaigns or search_campaigns. report_id: Abuse report ID. Obtain from get_campaign_abuse_reports.

Returns: JSON with id, campaign_id, list_id, email_id, email_address, date, merge_fields, vip.

Inputs: report_id (required), campaign_id (required), account. Returns: result

get_campaign_abuse_reportsA
Read-only

List abuse (spam) complaints filed against a sent campaign.

Use to monitor deliverability health; a high complaint count signals list quality or content issues. Use get_campaign_abuse_report for a single complaint's details. Use get_campaign_report for overall stats.

Args: campaign_id: Sent campaign ID. Obtain from list_campaigns or search_campaigns.

Returns: JSON with total_items and abuse_reports array. Each: id, campaign_id, list_id, email_id, email_address, date.

Inputs: campaign_id (required), account. Returns: result

get_campaign_adviceA
Read-only

Retrieve Mailchimp's automated post-send feedback on a campaign (subject line, content, engagement tips).

Use to surface algorithmic suggestions Mailchimp makes after looking at how a campaign performed (e.g. 'your open rate is below industry average, try shorter subject lines'). Use get_campaign_report for raw metrics. Only works for sent campaigns.

Returns 404 error if campaign_id is invalid. Returns an empty advice array if Mailchimp has no suggestions for the campaign.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Must be a sent campaign.

Returns: JSON with total_items and advice array. Each entry: type ('positive' | 'negative' | 'neutral'), message (string, the advice text).

Inputs: campaign_id (required), account. Returns: result

get_campaign_click_detailsA
Read-only

Retrieve per-link click data for a campaign showing which URLs were clicked and how many times.

Use to analyze which links drove engagement. Use get_campaign_report instead for aggregate totals (opens, clicks, bounces). Use get_email_activity for per-recipient click timelines. Only works for sent campaigns.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Number of URL results to return (1-1000, default 20).

Returns: JSON with total_items and links array. Each link: url (string), total_clicks (int, includes repeat clicks), unique_clicks (int, one per subscriber), click_percentage (decimal 0-1).

Example: get_campaign_click_details(campaign_id="abc123") -> {"total_items": 5, "links": [{"url": "https://example.com", "total_clicks": 120, "unique_clicks": 95, "click_percentage": 0.019}]}

Inputs: campaign_id (required), count, account. Returns: result

get_campaign_contentA
Read-only

Read the rendered body copy of a campaign (plain text, optionally HTML).

Use to retrieve the email copy that was actually sent, for content audits, analysis, or repurposing. Use get_campaign_details for settings/metadata (subject line, sender) and get_campaign_report for post-send performance. Use list_campaigns or search_campaigns to find campaign IDs.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Obtain from list_campaigns or search_campaigns. This is the API id, not the numeric web_id from the dashboard URL. include_html: When True, also return the raw HTML body. Defaults to False so responses stay compact; plain_text is enough for most content work.

Returns: JSON with campaign_id and plain_text (the plain-text body); html is added only when include_html=True. For A/B (variate) campaigns, a variations array is included with one entry per content variation: {label, plain_text, and html when include_html=True}. Very long bodies are capped (see MAILCHIMP_MAX_CONTENT_CHARS); when that happens a truncated field names the affected parts. Returns error if the campaign_id is invalid or the campaign has no content.

Example: get_campaign_content(campaign_id="abc123def4") -> {"campaign_id": "abc123def4", "plain_text": "Hi |FNAME| ..."}

Inputs: campaign_id (required), account, include_html. Returns: result

get_campaign_detailsA
Read-only

Retrieve full configuration of a specific campaign including settings, recipients, and tracking options.

Use to inspect subject line, sender, audience targeting, or tracking settings. Use get_campaign_report instead for post-send performance (opens, clicks, bounces). Use list_campaigns or search_campaigns to find campaign IDs.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Obtain from list_campaigns or search_campaigns.

Returns: JSON with fields: id, type, status, settings (subject_line, title, from_name, reply_to), recipients (list_id, segment_opts), send_time (ISO 8601 or null), emails_sent, tracking (opens, html_clicks, text_clicks booleans). Returns error if campaign_id is invalid.

Example: get_campaign_details(campaign_id="abc123def4") -> {"id": "abc123def4", "status": "sent", "settings": {"subject_line": "Spring Sale", ...}}

Inputs: campaign_id (required), account. Returns: result

get_campaign_feedbackA
Read-only

Retrieve a single team feedback comment on a campaign.

Use to read the full text and metadata of one collaboration comment. Use list_campaign_feedback to discover feedback IDs.

Args: campaign_id: Campaign ID the feedback belongs to. Obtain from list_campaigns. feedback_id: Feedback comment ID. Obtain from list_campaign_feedback.

Returns: JSON with feedback_id, message, is_complete, block_id, created_by, created_at, updated_at.

Inputs: campaign_id (required), feedback_id (required), account. Returns: result

get_campaign_folderA
Read-only

Retrieve details for a single campaign folder.

Use to confirm a folder's name and how many campaigns it contains before organizing campaigns. Use list_campaign_folders to discover folder IDs.

Args: folder_id: Campaign folder ID. Obtain from list_campaign_folders.

Returns: JSON with id, name, and count of campaigns in the folder.

Inputs: folder_id (required), account. Returns: result

get_campaign_locationsA
Read-only

Retrieve geographic open data for a sent campaign, broken down by country and region.

Use to map where opens happened — useful for region-targeted follow-ups, timezone-aware sending, or audit reports. Aggregated from IP geolocation at open time. Use get_domain_performance for per-provider stats instead. Only works for sent campaigns.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Number of locations to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and locations array. Each entry: country_code (ISO 2-letter, e.g. 'US'), region (string, state/province name or code), region_name (full name), opens (int, opens from that region).

Inputs: campaign_id (required), count, offset, account. Returns: result

get_campaign_recipientsA
Read-only

Retrieve the delivery roster for a sent campaign showing each recipient's delivery status and open count.

Use to verify who received a campaign and whether they opened it. Use get_email_activity for detailed per-recipient timelines (clicks, bounces with timestamps). Use get_campaign_report for aggregate metrics. Only works for sent campaigns; returns error for drafts or scheduled.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Number of recipients to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items (int) and recipients array. Each recipient: email_address, status ('sent', 'hard', 'soft'), open_count (int), last_open (ISO 8601 or null).

Example: get_campaign_recipients(campaign_id="abc123", count=100) -> {"total_items": 5000, "recipients": [{"email_address": "jane@co.com", "status": "sent", "open_count": 3, ...}]}

Inputs: campaign_id (required), count, offset, account. Returns: result

get_campaign_reportA
Read-only

Retrieve aggregate performance metrics for a sent campaign: opens, clicks, bounces, benchmarks.

High-level overview. Use get_campaign_click_details for per-link data, get_open_details for per-recipient opens, get_campaign_recipients for delivery status. Only works for sent campaigns.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be sent. Obtain from list_campaigns(status="sent").

Returns: JSON with campaign_title, subject_line, emails_sent, abuse_reports, unsubscribed, send_time, opens (opens_total, unique_opens, open_rate 0-1), clicks (clicks_total, unique_clicks, click_rate), bounces, forwards, list_stats, industry_stats.

Inputs: campaign_id (required), account. Returns: result

get_campaign_send_checklistA
Read-only

Retrieve the pre-send readiness checklist for a campaign.

Use to verify a campaign is ready before sending; the checklist flags missing recipients, subject lines, content, or other blockers. Resolve any 'error' type items before calling send_campaign. Use get_campaign_details to find campaign IDs.

Args: campaign_id: Campaign ID to check. Obtain from list_campaigns or search_campaigns.

Returns: JSON with is_ready (boolean) and items array. Each item: type ('success'/'warning'/'error'), id, heading, details.

Inputs: campaign_id (required), account. Returns: result

get_campaign_sent_toA
Read-only

List the members a sent campaign was delivered to, with per-recipient status.

Use to audit exactly who received a campaign and whether each delivery succeeded or bounced. Paginate with count and offset for large recipient lists. Use get_campaign_report for aggregate stats instead.

Args: campaign_id: Sent campaign ID. Obtain from list_campaigns or search_campaigns. count: Recipients to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and sent_to array. Each: email_id, email_address, status ('sent'/'bounced'), open_count, absplit_group, gmt_offset, merge_fields.

Inputs: campaign_id (required), count, offset, account. Returns: result

get_campaign_sub_reportsA
Read-only

Retrieve child report data for A/B test, variate, or RSS campaign sub-items.

Read-only, no side effects. Returns empty data for regular campaigns; use get_campaign_report instead. Check campaign type with get_campaign_details first ('absplit', 'variate', 'rss').

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Should be type 'absplit', 'variate', or 'rss'. Obtain from list_campaigns.

Returns: JSON with sub-reports. Format varies: A/B tests include per-variant opens, clicks, winner; RSS includes per-item send stats with dates.

Inputs: campaign_id (required), account. Returns: result

get_campaign_unsubscribesA
Read-only

Retrieve members who unsubscribed from a specific sent campaign, with reasons.

Use get_campaign_report for aggregate unsubscribe count instead.

Returns 404 error if campaign_id is invalid. Returns empty array for unsent campaigns.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Records to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and unsubscribes array. Each: email_address, reason (string or null), timestamp.

Inputs: campaign_id (required), count, offset, account. Returns: result

get_chimp_chatterA
Read-only

Retrieve the account activity feed (Chimp Chatter) of recent events across the account.

Use to review a chronological stream of account-wide activity such as sends, imports, and subscriber changes. Use get_campaign_report for metrics on a single campaign instead.

Args: count: Number of activity records to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and chimp_chatter array. Each entry: title, message, type, update_time, url, campaign_id, list_id.

Inputs: count, offset, account. Returns: result

get_connected_siteA
Read-only

Retrieve the full record for a single connected site including its tracking script.

Use when you have a connected site ID and need its script snippet or installation status. Use list_connected_sites to browse all sites and discover IDs instead.

Args: connected_site_id: The connected site ID to inspect. Obtain from list_connected_sites.

Returns: JSON with id, foreign_id, domain, site_script (object with url and fragment), status, created_at, updated_at.

Inputs: connected_site_id (required), account. Returns: result

get_domain_performanceA
Read-only

Retrieve campaign performance broken down by recipient email domain (gmail.com, outlook.com, etc.).

Use to identify deliverability issues with specific providers or compare engagement across domains. Use get_campaign_report for overall aggregate metrics. Only works for sent campaigns.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Must be a sent campaign.

Returns: JSON with total_items and domains array. Each domain: domain (string, e.g. 'gmail.com'), emails_sent (int), bounces (int), opens (int), clicks (int), unsubs (int).

Example: get_domain_performance(campaign_id="abc123") -> {"total_items": 15, "domains": [{"domain": "gmail.com", "emails_sent": 2000, "opens": 500, "clicks": 80, ...}]}

Inputs: campaign_id (required), account. Returns: result

get_ecommerce_product_activityA
Read-only

Retrieve e-commerce product activity for a campaign showing revenue per product.

Requires an active e-commerce integration; returns total_items: 0 if none is connected. Use list_ecommerce_stores to verify status. Only works for sent campaigns.

Returns 404 error if campaign_id is invalid.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Products to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and products array. Each: title, sku, image_url, total_revenue (float, store currency), total_purchased.

Inputs: campaign_id (required), count, offset, account. Returns: result

get_eepurl_activityA
Read-only

Retrieve social sharing stats for a campaign's eepurl (Mailchimp's short-URL share link).

Use to measure how much the campaign was shared on Twitter/Facebook/etc. via the 'Share this' link Mailchimp generates. Use get_campaign_click_details for in-email link clicks instead. Only works for sent campaigns where eepurl tracking is enabled.

Args: campaign_id: The Mailchimp campaign ID (e.g. 'abc123def4'). Must be a sent campaign.

Returns: JSON with eepurl (the short URL), twitter (object with statuses, first_status, last_status, replies, impressions, retweets), facebook (object with likes, recipient_likes, unique_likes), referrers array (list of {referrer, clicks, first_click, last_click}).

Inputs: campaign_id (required), account. Returns: result

get_email_activityA
Read-only

Retrieve per-recipient activity timeline for a sent campaign (opens, clicks, bounces).

Use get_open_details for open data only. Use get_campaign_report for aggregate totals. Use get_campaign_recipients for delivery status only.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Recipient records to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and emails array. Each: email_address, activity array with action ('open'/'click'/'bounce'), timestamp, url (clicks only).

Inputs: campaign_id (required), count, offset, account. Returns: result

get_fileA
Read-only

Retrieve full metadata for a single File Manager file.

Use when you have a file_id (from list_files) and need its hosted URL, dimensions, or folder. Use list_files to browse and discover file_ids.

Returns 404 error if file_id is invalid.

Args: file_id: File ID (numeric, as a string) from list_files.

Returns: JSON with id, name, type, full_size_url, thumbnail_url, size, width, height, folder_id, created_at, created_by.

Inputs: file_id (required), account. Returns: result

get_landing_pageA
Read-only

Retrieve full details of a landing page including description and tracking settings.

Use list_landing_pages to browse all pages and discover page IDs.

Returns 404 error if page_id is invalid.

Args: page_id: Landing page ID (alphanumeric string). Obtain from list_landing_pages.

Returns: JSON with id, name, title, description, status ('published'/'unpublished'/'draft'), url, published_at, created_at, updated_at, list_id, tracking.

Inputs: page_id (required), account. Returns: result

get_landing_page_reportA
Read-only

Get the report for a single landing page.

Retrieves the detailed performance report for one landing page identified by its outreach id. Use this to review visits, conversions, and other metrics for a specific page.

Args: outreach_id: The outreach id of the landing page to report on.

Returns: JSON with the landing page report.

Inputs: outreach_id (required), account. Returns: result

get_member_activityA
Read-only

Retrieve a member's email interaction history (opens, clicks, bounces across all campaigns).

Shows email actions only. Use get_member_events for custom API-triggered events. Use get_member_tags for tag data. Use search_members first to find which audience a member belongs to.

Returns 404 error if the member does not exist in the audience.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the member. Must exist in the audience. count: Number of activity records to return (1-1000, default 20).

Returns: JSON with email_address and activity array. Each: action ('open'/'click'/'bounce'), timestamp, campaign_id, title.

Inputs: list_id (required), email_address (required), count, account. Returns: result

get_member_eventsA
Read-only

Retrieve custom API-triggered events for a specific member (e.g. "purchased", "signed_up").

Use to view events sent to Mailchimp via the Events API. These are custom application events, not email interactions (opens, clicks); use get_member_activity for email engagement data. Returns empty if no custom events have been recorded for the member.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email address of the member. Must exist in the audience. count: Number of events to return (1-1000, default 20).

Returns: JSON with email_address, total_items (int), and events array. Each event: name (string, event name), occurred_at (ISO 8601), properties (object, custom key-value data or null).

Example: get_member_events(list_id="abc123", email_address="jane@co.com") -> {"email_address": "jane@co.com", "total_items": 5, "events": [{"name": "purchased", "occurred_at": "2025-06-01T10:00:00Z", "properties": {"product": "T-Shirt"}}]}

Inputs: list_id (required), email_address (required), count, account. Returns: result

get_member_goalsA
Read-only

Retrieve the last 50 Goal events triggered by a specific audience member.

Use to see which tracked website Goals (URL-based conversion events) a member has hit. Use get_member_activity for broader email activity or search_members to locate a member first.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: The member's email address. The subscriber hash is derived automatically.

Returns: JSON with total_items and goals array. Each: goal_id, event (the tracked value), last_visited_at (ISO 8601), data (the URL or event data). Returns error if the member is not found.

Inputs: list_id (required), email_address (required), account. Returns: result

get_member_journey_eventsA
Read-only

Retrieve a member's activity events filtered to automation- and journey-related actions.

Returns the subset of the member's activity feed that relates to Classic Automations and (where Mailchimp surfaces them) Customer Journey emails. Useful to answer "what automation or journey emails has this contact received?" without scanning their full activity.

Note: Mailchimp does not expose a public read API for Customer Journeys themselves. Journey emails do appear in the activity feed as automation-typed actions, so this tool surfaces them via that side-channel rather than reading the journey graph directly. Use trigger_customer_journey to enroll a contact into a specific journey step (the only journey write available via API).

Args: list_id: Audience/list ID (10-char alphanumeric). Obtain from list_audiences. email_address: Email of the member. Must exist in the audience. count: Number of activity rows to scan before filtering (1-1000, default 50). Raise if the member is highly active and you suspect automation events are missed.

Returns: JSON with email_address, scanned (raw row count looked at), total_journey_events (after filtering), and events array. Each event: action (raw action type), timestamp, title (campaign / automation title if present), url (link clicked if any), campaign_id.

Inputs: list_id (required), email_address (required), count, account. Returns: result

get_member_tagsA
Read-only

Retrieve all tags currently assigned to a specific member.

Use to see which tags a member has before modifying them. Use tag_member to add or remove tags. Use list_segments to see all available tags/segments in the audience.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email address of the member. Must exist in the audience. count: Number of tags to return (1-1000, default 50).

Returns: JSON with email_address, total_items (int), and tags array. Each tag: id (int), name (string), date_added (ISO 8601).

Example: get_member_tags(list_id="abc123", email_address="jane@co.com") -> {"email_address": "jane@co.com", "total_items": 3, "tags": [{"name": "VIP", "date_added": "2025-01-15T10:00:00Z", ...}]}

Inputs: list_id (required), email_address (required), count, account. Returns: result

get_open_detailsA
Read-only

Retrieve per-recipient open data for a sent campaign (who opened, when, how many times).

Use get_campaign_report for aggregate open rates. Use get_email_activity for all activity types combined.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Records to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and members array. Each: email_address, opens_count, opens array with timestamps.

Inputs: campaign_id (required), count, offset, account. Returns: result

get_promo_codeA
Read-only

Retrieve a single promo code by ID with its current settings and usage stats.

Use to check a code's usage_count before a campaign, or confirm a code is enabled. Use list_promo_codes to browse codes for a rule.

Returns 404 if any of store_id, promo_rule_id, or promo_code_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID the code is attached to. promo_code_id: Code ID to inspect.

Returns: JSON with id, code, redemption_url, usage_count, enabled, created_at, updated_at.

Inputs: store_id (required), promo_code_id (required), promo_rule_id (required), account. Returns: result

get_promo_ruleA
Read-only

Retrieve a single promo rule by ID with its full configuration.

Use to inspect a rule's current settings before updating, or to confirm a rule exists before attaching new codes. Use list_promo_rules to browse and discover IDs.

Returns 404 if store_id or promo_rule_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID to inspect.

Returns: JSON with id, title, description, amount, type, target, enabled, starts_at, ends_at, created_at, updated_at.

Inputs: store_id (required), promo_rule_id (required), account. Returns: result

get_segmentA
Read-only

Retrieve full details of a specific segment including member count and filter conditions.

Use to inspect a segment's conditions or verify its type and member count. Use list_segments to browse all segments. Use list_segment_members to see individual members in the segment.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. segment_id: The segment ID (numeric string, e.g. '12345'). Obtain from list_segments.

Returns: JSON with fields: id, name, member_count (int), type ('static' for tags, 'saved' for dynamic segments), created_at (ISO 8601), updated_at (ISO 8601), options (object with match and conditions for dynamic segments, null for static segments).

Example: get_segment(list_id="abc123", segment_id="12345") -> {"id": 12345, "name": "VIP", "member_count": 150, "type": "static", ...}

Inputs: list_id (required), segment_id (required), account. Returns: result

get_storeA
Read-only

Retrieve a single e-commerce store with its configuration and connection details.

Use to inspect a store's currency, connected audience, and sync status. Use list_ecommerce_stores to browse and discover store_ids.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores.

Returns: JSON with the store object.

Inputs: store_id (required), account. Returns: result

get_store_cartA
Read-only

Retrieve a single cart with its full line items, customer, and total breakdown.

Use to inspect what's in an abandoned cart before triggering a recovery email. Use list_store_carts to browse and discover cart_ids.

Returns 404 if store_id or cart_id is invalid.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. cart_id: Cart ID. Obtain from list_store_carts.

Returns: JSON with id, customer, currency_code, order_total, tax_total, checkout_url, lines (array of {id, product_id, product_variant_id, quantity, price}), created_at, updated_at.

Inputs: cart_id (required), store_id (required), account. Returns: result

get_store_customerA
Read-only

Retrieve a single store customer with their email, opt-in status, and order totals.

Use to inspect a customer's purchase history and subscription state. Use list_store_customers to browse and discover customer_ids.

Args: store_id: E-commerce store ID. customer_id: Customer ID. Obtain from list_store_customers.

Returns: JSON with the customer object.

Inputs: store_id (required), customer_id (required), account. Returns: result

get_store_orderA
Read-only

Retrieve a single e-commerce order with its lines, customer, and totals.

Use to inspect one order's full detail after finding it via list_store_orders or list_account_orders. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync orders automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID within the store. Obtain from list_store_orders.

Returns: JSON with the full order object (id, customer, currency_code, order_total, lines, financial_status, processed_at_foreign, and related fields).

Inputs: order_id (required), store_id (required), account. Returns: result

get_store_order_lineA
Read-only

Retrieve a single line item from an e-commerce order.

Use to inspect one product entry's quantity, price, and discount within an order. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync order lines automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID that owns the line. line_id: Line item ID. Obtain from list_store_order_lines.

Returns: JSON with the line object (id, product_id, product_variant_id, quantity, price, discount).

Inputs: line_id (required), order_id (required), store_id (required), account. Returns: result

get_store_productA
Read-only

Retrieve a single product from a store with its variants and details.

Use to inspect a product's title, variants, images, and pricing. Use list_store_products to browse and discover product_ids.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID. Obtain from list_store_products.

Returns: JSON with the product object including its variants array.

Inputs: store_id (required), product_id (required), account. Returns: result

get_store_product_imageA
Read-only

Retrieve a single image attached to a product in an e-commerce store.

Use to inspect one image's URL and variant associations. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID that owns the image. image_id: Image ID. Obtain from list_store_product_images.

Returns: JSON with the image object (id, url, variant_ids).

Inputs: image_id (required), store_id (required), product_id (required), account. Returns: result

get_store_product_variantA
Read-only

Retrieve a single product variant with its price, SKU, and inventory details.

Use to inspect one variant's attributes. Use list_store_product_variants to browse and discover variant_ids.

Args: store_id: E-commerce store ID. product_id: Product ID that owns the variant. variant_id: Variant ID. Obtain from list_store_product_variants.

Returns: JSON with the variant object.

Inputs: store_id (required), product_id (required), variant_id (required), account. Returns: result

get_surveyA
Read-only

Retrieve full details for a single survey.

Use when you have a survey_id (from list_surveys) and need its questions, status, or public URL. Use publish_survey / unpublish_survey to change whether it is live.

Returns 404 error if list_id or survey_id is invalid.

Args: list_id: Audience/list ID (from list_audiences). survey_id: Survey ID (from list_surveys).

Returns: JSON survey object including id, title, status, url, questions, created_at, updated_at.

Inputs: list_id (required), survey_id (required), account. Returns: result

get_survey_question_answersA
Read-only

List answers for a single survey question.

Retrieves the individual answers submitted for one specific question within the specified survey. Use count and offset to page through large result sets.

Args: survey_id: The unique id of the survey. question_id: The unique id of the question whose answers to list. count: Number of records to return per page (default 10). offset: Number of records to skip for pagination (default 0).

Returns: JSON with the list of survey question answers.

Inputs: survey_id (required), question_id (required), count, offset, +1 more. Returns: result

get_survey_questions_reportA
Read-only

Get the questions report for a single survey.

Retrieves aggregate reporting broken down by each question in the specified survey. Use this to understand how respondents answered across all questions.

Args: survey_id: The unique id of the survey whose questions to report on.

Returns: JSON with the survey questions report.

Inputs: survey_id (required), account. Returns: result

get_survey_reportA
Read-only

Get the report for a single survey.

Retrieves the detailed performance report for one survey identified by its id. Use this to review response rates and engagement for a specific survey.

Args: survey_id: The unique id of the survey to report on.

Returns: JSON with the survey report.

Inputs: survey_id (required), account. Returns: result

get_survey_responseA
Read-only

Get a single survey response.

Retrieves the details of one specific response submitted to the specified survey. Use this to inspect the answers of an individual respondent.

Args: survey_id: The unique id of the survey. response_id: The unique id of the response to retrieve.

Returns: JSON with the survey response details.

Inputs: survey_id (required), response_id (required), account. Returns: result

get_survey_responsesB
Read-only

List responses for a single survey.

Retrieves the individual responses submitted to the specified survey. Use count and offset to page through large result sets.

Args: survey_id: The unique id of the survey whose responses to list. count: Number of records to return per page (default 10). offset: Number of records to skip for pagination (default 0).

Returns: JSON with the list of survey responses.

Inputs: survey_id (required), count, offset, account. Returns: result

get_templateA
Read-only

Retrieve metadata for a template (name, type, dates, folder, thumbnail) without its HTML content.

Use to inspect a template's settings or verify it exists before referencing it elsewhere. Use get_template_default_content to fetch the actual HTML body. Use list_templates to browse and discover template IDs.

Returns 404 error if template_id is invalid.

Args: template_id: Template ID (numeric string, e.g. '12345'). Obtain from list_templates.

Returns: JSON with id, name, type ('user' | 'base' | 'gallery'), drag_and_drop (bool), date_created, date_edited, created_by, edited_by, active (bool), folder_id, thumbnail, share_url, category.

Inputs: template_id (required), account. Returns: result

get_template_default_contentA
Read-only

Retrieve the default HTML content of a template for use in campaign content.

Use to extract a template's HTML before customizing it with set_campaign_content. Only works for user-created templates; gallery templates may return limited content. Use list_templates to find template IDs.

Returns 404 error if template_id is invalid.

Args: template_id: Template ID (numeric string, e.g. '12345'). Obtain from list_templates.

Returns: JSON with html (string, full HTML content), sections (object with editable content blocks).

Inputs: template_id (required), account. Returns: result

get_template_folderA
Read-only

Retrieve details for a single template folder.

Use to confirm a folder's name and how many templates it contains. Use list_template_folders to discover folder IDs.

Args: folder_id: Template folder ID. Obtain from list_template_folders.

Returns: JSON with id, name, and count of templates in the folder.

Inputs: folder_id (required), account. Returns: result

get_verified_domainA
Read-only

Retrieve the full verification and authentication record for a single sending domain.

Use when you have a domain name and need its exact verified/authenticated state before sending. Use list_verified_domains to browse all domains and discover names instead.

Args: domain_name: The sending domain to inspect (e.g. 'mail.example.com'). Obtain from list_verified_domains.

Returns: JSON with domain, verified (boolean), authenticated (boolean), verification_status, authentication_status.

Inputs: domain_name (required), account. Returns: result

list_account_exportsA
Read-only

List account export jobs that have been requested for this Mailchimp account.

Use this to track export requests and discover export IDs and their status. Use get_account_export for the full record and download URL of a single export.

Returns: JSON with total_items and exports array. Each export: export_id, status, started (ISO 8601), finished (ISO 8601 or null), size_in_bytes, download_url.

Inputs: account. Returns: result

list_account_ordersA
Read-only

List e-commerce orders across every store in the account.

Use for account-wide order reporting without iterating store by store; scope to a single store with list_store_orders instead. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync orders automatically.

Args: count: Number of orders to return (max 1000). Defaults to 10. offset: Number of orders to skip for pagination. Defaults to 0.

Returns: JSON with orders (array of order objects across all stores), total_items.

Inputs: count, offset, account. Returns: result

list_accountsA
Read-only

List the Mailchimp accounts this server is configured to use.

Use this to discover the account names accepted by the account argument on every other tool. Multi-account support is opt-in: define extra accounts with MAILCHIMP_API_KEY_ environment variables; the plain MAILCHIMP_API_KEY is the implicit 'default'. Selection is per call and stateless -- no tool changes an active account. Use get_account_info for live stats about a specific account.

No network call. Never returns API keys or any secret material.

Returns: JSON with accounts: an array of {name, read_only, dry_run, is_default}. The 'default' entry appears only when MAILCHIMP_API_KEY is set.

Inputs: no named parameters. Returns: result

list_audience_abuse_reportsA
Read-only

List abuse (spam) complaint reports filed against an audience.

Use to monitor deliverability health and identify campaigns generating spam complaints. Use get_audience_abuse_report to inspect a single report in detail.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. count: Number of abuse reports to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and abuse_reports array. Each: id (report_id), campaign_id, list_id, email_id, email_address, date (ISO 8601 when the complaint was filed).

Inputs: list_id (required), count, offset, account. Returns: result

list_audience_membersA
Read-only

List members of a specific audience with subscription status, merge fields, and engagement stats.

Use to browse members of a known audience. Use search_members instead to find a specific person by email or name across all audiences. Use list_segment_members to list members of a specific segment/tag.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. count: Number of members to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count. status: Filter by subscription status. Valid values: 'subscribed', 'unsubscribed', 'cleaned', 'pending', 'transactional'. Omit to return all statuses.

Returns: JSON with total_items and members array. Each member: id (MD5 hash of email), email_address, status, full_name, merge_fields (object with FNAME, LNAME, etc.), open_rate (decimal 0-1), click_rate (decimal 0-1), timestamp_opt (ISO 8601 opt-in time).

Example: list_audience_members(list_id="abc123", count=50, status="subscribed") -> {"total_items": 5000, "members": [{"email_address": "jane@co.com", "status": "subscribed", ...}]}

Inputs: list_id (required), count, offset, status, +1 more. Returns: result

list_audiencesA
Read-only

List audiences (lists) with subscriber counts and engagement rates.

First step in most workflows to discover list_id values. Use get_audience_details for full stats of a known audience. Use search_members to find a specific member.

Args: count: Audiences to return (1-1000, default 10). Most accounts have fewer than 10. offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and audiences array. Each: id (use as list_id), name, member_count, unsubscribe_count, open_rate (0-1), click_rate (0-1), date_created, and the audience settings carried in the same list payload: campaign_defaults (default from_name, from_email, subject, language), double_optin (bool: true = confirmed/double opt-in), marketing_permissions (bool: GDPR permission fields enabled). These settings come free with this call -- the /lists endpoint returns each list's full object -- so all audiences and their opt-in/sender/compliance config are available in one request, without a get_audience_details call per audience.

Inputs: count, offset, account. Returns: result

list_authorized_appsA
Read-only

List applications that have been granted OAuth access to this Mailchimp account.

Use this to audit which third-party apps are connected and discover their IDs. Use get_authorized_app for the full record of a single app.

Returns: JSON with total_items and apps array. Each app: id, name, description, users (array of account usernames that authorized it).

Inputs: account. Returns: result

list_automation_removed_subscribersA
Read-only

List subscribers removed from a classic automation workflow.

Retrieves all subscribers who have been removed from the specified automation workflow. Removed subscribers no longer receive any emails in the workflow.

Args: workflow_id: The unique id of the classic automation workflow.

Returns: JSON with the list of removed subscribers.

Inputs: workflow_id (required), account. Returns: result

list_automationsA
Read-only

List Classic Automation workflows in the account with status and send counts.

Returns Classic Automations only — ordered by creation date descending. Customer Journeys are NOT returned (Mailchimp does not expose a public read endpoint for journeys; only the journey-step trigger endpoint is public). To see what your Customer Journeys are sending, use search_automation_campaigns instead (it lists every campaign emitted by either system). Use get_automation_emails for individual emails within a Classic workflow. Use get_automation_summary for a counted overview combining both systems.

Args: count: Automations to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and automations array. Each: id, status ('sending'/'paused'/'draft'), title, emails_sent, start_time, create_time, list_id.

Inputs: count, offset, account. Returns: result

list_batchesA
Read-only

List recent batch operations with status and progress.

Use get_batch_status for detailed progress on a specific batch.

Args: count: Batch operations to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and batches array. Each: id, status ('pending'/'started'/'finished'), total_operations, finished_operations, errored_operations, submitted_at, completed_at.

Inputs: count, offset, account. Returns: result

list_batch_webhooksA
Read-only

List all configured batch webhooks for the account.

Batch webhooks notify a URL when a batch operation finishes. Use to discover batch_webhook_id values, and get_batch_webhook to inspect one in detail.

Returns: JSON with total_items and webhooks array. Each: id (batch_webhook_id), url, enabled (boolean).

Inputs: account. Returns: result

list_campaign_feedbackA
Read-only

List team collaboration feedback comments on a campaign.

Use to review internal notes and review comments left by team members during campaign preparation. Use get_campaign_feedback for a single comment's details. Use get_campaign_details to find campaign IDs.

Args: campaign_id: Campaign ID whose feedback to list. Obtain from list_campaigns or search_campaigns.

Returns: JSON with total_items and feedback array. Each: feedback_id, message, is_complete, block_id, created_by, created_at, updated_at.

Inputs: campaign_id (required), account. Returns: result

list_campaign_foldersA
Read-only

List campaign folders used to organize campaigns in the Mailchimp dashboard.

Folders are organizational containers only; they do not affect campaign delivery or behavior. Returns an empty array if no folders exist. Do not use to find campaigns; use list_campaigns or search_campaigns instead.

Args: count: Number of folders to return (1-1000, default 50). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and folders array. Each folder: id, name, count (campaigns in folder).

Inputs: count, offset, account. Returns: result

list_campaignsA
Read-only

List campaigns with metadata, send stats, and filtering by status or date.

Use to browse campaigns and discover campaign IDs. Use get_campaign_details for full settings of a single campaign. Use get_campaign_report for post-send performance metrics. Use search_campaigns to find campaigns by keyword instead of browsing.

Args: count: Number of campaigns to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count. status: Filter by status. Valid values: 'save' (draft), 'paused', 'schedule', 'sending', 'sent'. Omit to return all statuses. since_send_time: Only return campaigns sent after this datetime. ISO 8601 format (e.g. '2025-01-01T00:00:00Z'). Only applies to sent campaigns.

Returns: JSON with total_items and campaigns array. Each campaign: id, type ('regular', 'plaintext', 'absplit', 'rss', 'variate'), status, title, subject_line, preview_text, send_time (ISO 8601 or null), emails_sent, list_id, list_name.

Example: list_campaigns(count=10, status="sent") -> {"total_items": 42, "campaigns": [{"id": "abc123", "status": "sent", ...}]}

Inputs: count, offset, status, account, +1 more. Returns: result

list_connected_sitesA
Read-only

List all sites connected to this Mailchimp account for tracking and pop-up forms.

Use this to discover connected site IDs and check each site's script installation status. Use get_connected_site for the full record of a single site.

Returns: JSON with total_items and sites array. Each site: id, foreign_id, domain, site_script (object with url and fragment), status, created_at, updated_at.

Inputs: account. Returns: result

list_ecommerce_storesA
Read-only

List connected e-commerce stores (Shopify, WooCommerce, etc.) with platform and currency info.

Use to discover store IDs for list_store_orders, list_store_products, list_store_customers. Also verifies integration status before get_ecommerce_product_activity. Returns total_items: 0 if no integration is configured.

Returns: JSON with total_items and stores array. Each: id (use as store_id), list_id, name, platform, domain, currency_code (ISO 4217), money_format, created_at.

Inputs: account. Returns: result

list_file_foldersA
Read-only

List folders in the account's File Manager.

Use to discover folder_id values for organizing or targeting uploads via upload_file. Use list_files to see the files themselves.

Args: count: Folders to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and folders array. Each folder: id (use as folder_id), name, file_count, created_at, created_by.

Inputs: count, offset, account. Returns: result

list_filesA
Read-only

List images and files stored in the account's File Manager.

Use to discover file_id and hosted URLs for embedding images in campaign or template content. Use get_file for one file's full metadata, upload_file to add a new one, and list_file_folders to browse the folder structure.

Args: count: Files to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count. type: Optional media type filter. Either 'image' or 'file' (non-image). Omit for all.

Returns: JSON with total_items and files array. Each file: id (use as file_id), name, type ('image' or 'file'), full_size_url (hosted URL for embedding), thumbnail_url, size (bytes), width, height, folder_id, created_at, created_by.

Inputs: type, count, offset, account. Returns: result

list_interest_categoriesA
Read-only

List interest categories (group containers) for an audience, showing titles and form types.

Use to discover category IDs, then list_interests for options within each. Use create_interest_category to add new categories.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. count: Categories to return (1-1000, default 50). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and categories array. Each: id, title, type ('checkboxes'/'dropdown'/ 'radio'/'hidden'), list_id.

Inputs: list_id (required), count, offset, account. Returns: result

list_interestsA
Read-only

List interest options within a category, with subscriber counts per option.

Use after list_interest_categories to see individual options (e.g. "Tech", "Sports"). Interest IDs are needed when setting member preferences via add_member/update_member. Do not use to manage member preferences directly; set interests per-member via the API instead.

Returns 404 error if category_id is invalid.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. category_id: Interest category ID. Obtain from list_interest_categories. count: Number of interests to return (1-1000, default 50). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and interests array. Each interest: id, name, subscriber_count, display_order.

Inputs: list_id (required), category_id (required), count, offset, +1 more. Returns: result

list_landing_page_reportsA
Read-only

List reports for all landing pages.

Retrieves aggregate performance reports across every landing page in the account. Use count and offset to page through large result sets.

Args: count: Number of records to return per page (default 10). offset: Number of records to skip for pagination (default 0).

Returns: JSON with the list of landing page reports.

Inputs: count, offset, account. Returns: result

list_landing_pagesA
Read-only

List landing pages with publication status, URLs, and associated audiences.

Landing pages are standalone web pages, not emails. Use get_landing_page for full details. Do not use to find email campaigns; use list_campaigns instead.

Args: count: Landing pages to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and landing_pages array. Each: id, name, title, status ('published'/'unpublished'/'draft'), url (null if not published), published_at, created_at, list_id.

Inputs: count, offset, account. Returns: result

list_member_notesA
Read-only

List CRM-style notes attached to a member by team members (not visible to the contact).

Notes are internal annotations like "Called about pricing" or "VIP customer". They are not sent to the contact and do not affect deliverability. Use add_member_note to create one, update_member_note to edit, delete_member_note to remove.

Returns 404 error if the member does not exist.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the member whose notes to list. Must exist in the audience. count: Number of notes to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with email_address, total_items, and notes array. Each note: id (use as note_id), note (string, the text), created_at, created_by, updated_at.

Inputs: list_id (required), email_address (required), count, offset, +1 more. Returns: result

list_merge_fieldsA
Read-only

List merge fields (custom data fields) defined for an audience, including tags, types, and defaults.

Use to discover available merge fields and their tag names before adding or updating members. Default fields (FNAME, LNAME, ADDRESS, PHONE) are always present. Use create_merge_field to add custom fields. Merge field tags are used in add_member/update_member merge_fields objects and in email content as |TAG| merge tags.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. count: Number of merge fields to return (1-1000, default 50). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and merge_fields array. Each field: merge_id (int, use with update_merge_field/delete_merge_field), tag (string, e.g. 'FNAME'), name (display name), type ('text', 'number', 'date', etc.), required (boolean), default_value, options (choices for dropdown/radio types).

Example: list_merge_fields(list_id="abc123") -> {"total_items": 6, "merge_fields": [{"merge_id": 1, "tag": "FNAME", "name": "First Name", "type": "text", ...}]}

Inputs: list_id (required), count, offset, account. Returns: result

list_promo_codesA
Read-only

List the redeemable codes attached to a promo rule (e.g. 'SUMMER20', 'VIPONLY').

Codes are what customers type at checkout. They redeem the discount defined by the rule. A single rule can have many codes (e.g. one per customer segment).

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID. Obtain from list_promo_rules. count: Number of codes to return (1-1000, default 20). offset: Pagination offset.

Returns: JSON with store_id, promo_rule_id, total_items, and promo_codes array. Each code: id, code (the string customers type), redemption_url, usage_count, enabled, created_at, updated_at.

Inputs: store_id (required), promo_rule_id (required), count, offset, +1 more. Returns: result

list_promo_rulesA
Read-only

List discount/promo rules configured for a store (fixed amount, percentage, free shipping).

A promo rule defines the discount mechanic (e.g. '20% off entire order'). Codes that customers redeem are attached to rules via list_promo_codes / create_promo_code.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. count: Number of rules to return (1-1000, default 20). offset: Pagination offset.

Returns: JSON with store_id, total_items, and promo_rules array. Each rule: id, title, description, amount, type ('fixed' | 'percentage'), target ('per_item' | 'total' | 'shipping'), enabled (bool), starts_at, ends_at, created_at, updated_at.

Inputs: store_id (required), count, offset, account. Returns: result

list_segment_membersA
Read-only

List individual members belonging to a specific segment or tag.

Use to see who is in a segment. Use list_audience_members to browse all members of the full audience instead. Use get_segment to check segment metadata and member count first.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. segment_id: The segment ID (numeric string, e.g. '12345'). Obtain from list_segments. count: Number of members to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and members array. Each member: id, email_address, status, full_name, merge_fields (object with FNAME, LNAME, etc.).

Example: list_segment_members(list_id="abc123", segment_id="12345", count=50) -> {"total_items": 150, "members": [{"email_address": "jane@co.com", ...}]}

Inputs: list_id (required), segment_id (required), count, offset, +1 more. Returns: result

list_segmentsA
Read-only

List segments and tags for an audience with member counts and types.

Use to discover segment IDs for campaign targeting or membership management. Returns both static (tags, manual) and dynamic (saved, auto-updated) segments. Use get_segment for full details including filter conditions.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. count: Segments to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and segments array. Each: id (use as segment_id), name, member_count, type ('static'/'saved'), created_at, updated_at.

Inputs: list_id (required), count, offset, account. Returns: result

list_signup_formsA
Read-only

Get the signup forms (header, body content, and styles) configured for an audience.

Use to inspect the current hosted and embedded signup forms before changing them with customize_signup_form.

Returns 404 error if list_id is invalid.

Args: list_id: Audience/list ID (from list_audiences).

Returns: JSON with signup_forms array. Each entry has header (object), contents (array of {section, value}), styles (array of {section, options}), and signup_form_url.

Inputs: list_id (required), account. Returns: result

list_store_cartsA
Read-only

List carts for a store, including abandoned ones, with customer and total info.

Carts in Mailchimp typically represent in-progress purchases synced from a connected storefront. Use for abandoned-cart workflows: filter by recent created_at, segment by cart total, then trigger a recovery automation. Use get_store_cart for a single cart with line items. Use list_store_orders for completed purchases.

Returns 404 if store_id is invalid.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. count: Number of carts to return (1-1000, default 20). offset: Pagination offset.

Returns: JSON with store_id, total_items, and carts array. Each cart: id, customer (object with id, email_address, opt_in_status), currency_code, order_total, tax_total, checkout_url, created_at, updated_at.

Inputs: store_id (required), count, offset, account. Returns: result

list_store_customersA
Read-only

List customers from a connected e-commerce store with order counts, total spend, and opt-in status.

Use to analyze customer purchasing behavior or identify high-value customers. Requires an active e-commerce integration. Use list_ecommerce_stores to find store IDs. Use list_store_orders for per-order detail instead of customer-level aggregates.

Args: store_id: The e-commerce store ID. Obtain from list_ecommerce_stores. count: Number of customers to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and customers array. Each customer: id (string), email_address, first_name, last_name, orders_count (int), total_spent (float, in store currency), opt_in_status (boolean), created_at (ISO 8601).

Example: list_store_customers(store_id="store123", count=50) -> {"total_items": 500, "customers": [{"email_address": "jane@co.com", "orders_count": 5, "total_spent": 299.95, ...}]}

Inputs: store_id (required), count, offset, account. Returns: result

list_store_order_linesA
Read-only

List the line items of a single e-commerce order.

Use to review the individual products, quantities, and prices attached to an order. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync order lines automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID whose lines to list. count: Number of lines to return (max 1000). Defaults to 10. offset: Number of lines to skip for pagination. Defaults to 0.

Returns: JSON with lines (array of {id, product_id, product_variant_id, quantity, price, discount}), total_items.

Inputs: order_id (required), store_id (required), count, offset, +1 more. Returns: result

list_store_ordersA
Read-only

List orders from a connected e-commerce store with totals and fulfillment status.

Requires an active integration. Use list_store_customers for customer-level aggregates instead.

Args: store_id: E-commerce store ID (alphanumeric string). Obtain from list_ecommerce_stores. count: Orders to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and orders array. Each: id, customer (email), order_total (float), currency_code (ISO 4217), financial_status, fulfillment_status, processed_at_foreign, lines_count.

Inputs: store_id (required), count, offset, account. Returns: result

list_store_product_imagesA
Read-only

List the images attached to a product in an e-commerce store.

Use to review the image URLs and variant associations for a product before adding or updating them. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID whose images to list. Obtain from list_store_products. count: Number of images to return (max 1000). Defaults to 10. offset: Number of images to skip for pagination. Defaults to 0.

Returns: JSON with images (array of {id, url, variant_ids}), total_items.

Inputs: store_id (required), product_id (required), count, offset, +1 more. Returns: result

list_store_productsA
Read-only

List products from a connected e-commerce store with titles, URLs, and variant counts.

Use to browse the product catalog synced to Mailchimp. Useful for verifying sync status or finding product data for campaign content. Use list_ecommerce_stores to find store IDs. Use get_ecommerce_product_activity for campaign-level product revenue data.

Args: store_id: The e-commerce store ID. Obtain from list_ecommerce_stores. count: Number of products to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and products array. Each product: id (string), title, url (product page link), vendor (string), image_url (string or null), variants_count (int). Returns total_items: 0 if no integration is configured.

Example: list_store_products(store_id="store123", count=50) -> {"total_items": 200, "products": [{"id": "prod_123", "title": "Blue T-Shirt", "variants_count": 3, ...}]}

Inputs: store_id (required), count, offset, account. Returns: result

list_store_product_variantsA
Read-only

List the variants of a product in a store, with pagination.

Use to browse a product's variants and discover variant_ids. Increase offset to page through large variant sets.

Args: store_id: E-commerce store ID. product_id: Product ID whose variants to list. count: Number of variants to return (default 10, max 1000). offset: Number of variants to skip for pagination (default 0).

Returns: JSON with a variants array and total_items.

Inputs: store_id (required), product_id (required), count, offset, +1 more. Returns: result

list_survey_reportsA
Read-only

List reports for all surveys.

Retrieves aggregate performance reports across every survey in the account. Use count and offset to page through large result sets.

Args: count: Number of records to return per page (default 10). offset: Number of records to skip for pagination (default 0).

Returns: JSON with the list of survey reports.

Inputs: count, offset, account. Returns: result

list_surveysA
Read-only

List all surveys for an audience with their status and public URL.

Use to discover survey_id values and see which surveys are live. Use get_survey for one survey's full detail, and publish_survey / unpublish_survey to change its live state.

Returns 404 error if list_id is invalid.

Args: list_id: Audience/list ID (from list_audiences).

Returns: JSON with total_items and surveys array. Each survey typically includes id (use as survey_id), title, status ('draft', 'published', or 'unpublished'), url (public survey URL), created_at, updated_at.

Inputs: list_id (required), account. Returns: result

list_template_foldersA
Read-only

List folders used to organize templates.

Use to discover template folder IDs before creating or organizing templates. Paginate with count and offset when total_items exceeds count.

Args: count: Folders to return (1-1000, default 10). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and folders array. Each: id, name, count of templates.

Inputs: count, offset, account. Returns: result

list_templatesA
Read-only

List email templates in the account (user-created and Mailchimp gallery templates).

Use to browse templates and find template IDs. Use get_template_default_content to extract HTML from a template. Use create_template to add new templates. Do not use to find campaigns; use list_campaigns instead.

Args: count: Templates to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and templates array. Each: id (int), name, type ('user'/'gallery'/ 'base'), date_created, active (boolean).

Inputs: count, offset, account. Returns: result

list_verified_domainsA
Read-only

List all sending domains verified for use with this Mailchimp account.

Use this to discover which domains are approved as the "from" address on campaigns and to check each domain's verification and authentication state. Use get_verified_domain for the full record of a single domain.

Returns: JSON with total_items and domains array. Each domain: domain, verified (boolean), authenticated (boolean), verification_status, authentication_status.

Inputs: account. Returns: result

list_webhooksA
Read-only

List webhooks configured for an audience, showing callback URLs, events, and source filters.

Use to audit integrations or find webhook IDs before deleting via delete_webhook. Do not use to check webhook delivery history; Mailchimp does not expose delivery logs via the API.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences.

Returns: JSON with total_items and webhooks array. Each webhook: id, url, events (boolean flags: subscribe, unsubscribe, profile, cleaned, upemail, campaign), sources (boolean flags: user, admin, api), list_id.

Inputs: list_id (required), account. Returns: result

pause_automationA

Pause an automation workflow, stopping delivery while preserving the queue.

Queued subscribers resume when restarted via start_automation. New subscribers still enter the queue but do not receive emails while paused. Reversible.

Args: automation_id: Automation workflow ID (e.g. 'auto123'). Obtain from list_automations.

Returns: JSON with status ("paused"), automation_id. Error if already paused or in draft status.

Inputs: automation_id (required), account. Returns: result

pause_automation_emailA

Pause a specific email in a classic automation workflow.

Halts sending for a single automation email without pausing the entire workflow. Subscribers already queued remain queued until the email is started again.

Args: workflow_id: The unique id of the classic automation workflow. workflow_email_id: The unique id of the automation email to pause.

Returns: JSON confirming the pause action.

Inputs: workflow_id (required), workflow_email_id (required), account. Returns: result

pause_rss_campaignA

Pause an active RSS-driven campaign so it stops sending scheduled editions.

Use to temporarily halt an RSS campaign; resume later with resume_rss_campaign. Applies only to campaigns of type 'rss'. Use get_campaign_details to confirm the campaign type.

Args: campaign_id: RSS campaign ID to pause. Obtain from list_campaigns or search_campaigns.

Returns: JSON with the API response confirming the pause action, or an error if not an RSS campaign.

Inputs: campaign_id (required), account. Returns: result

pingA
Read-only

Check API connectivity and verify the API key is valid.

Fastest health check available. Use get_account_info instead if you need account details. Returns error object if the key is invalid or missing.

Returns: JSON with health_check ('ok' if connected), status_code (200 if healthy).

Inputs: account. Returns: result

publish_landing_pageA
Idempotent

Publish a landing page, making it live at its public URL.

Idempotent on already-published pages. Use unpublish_landing_page to take a page offline. Use get_landing_page to confirm the live URL after publishing.

Returns 400 if the page is missing required content; returns 404 if page_id is invalid.

Args: page_id: Landing page ID to publish. Obtain from list_landing_pages.

Returns: JSON with status ('published') and page_id on success.

Inputs: page_id (required), account. Returns: result

publish_surveyA

Publish a survey, making it live at its public URL.

Works for surveys in draft, unpublished, or previously-published-then-edited state. Use list_surveys to find the survey_id and check its status. Use unpublish_survey to take it back down.

Args: list_id: Audience/list ID (from list_audiences). survey_id: Survey ID (from list_surveys).

Returns: JSON with status 'published' and the survey_id, or an error object.

Inputs: list_id (required), survey_id (required), account. Returns: result

remove_automation_subscriberA

Remove a subscriber from a classic automation workflow.

Permanently removes a subscriber from the specified automation workflow so they receive no further emails. This action cannot be undone through the API.

Args: workflow_id: The unique id of the classic automation workflow. email_address: The email address of the subscriber to remove.

Returns: JSON confirming the removed subscriber.

Inputs: workflow_id (required), email_address (required), account. Returns: result

remove_members_from_segmentA

Remove members from a static segment or tag. Members remain in the audience.

Only works on static segments (tags), not dynamic segments. Non-existent members in the email list are silently skipped. Use tag_member with tags_to_remove for single-member removal.

Returns 404 error if segment_id or list_id is invalid.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. segment_id: Static segment/tag ID (numeric string, e.g. '12345'). Obtain from list_segments. emails: Comma-separated email addresses to remove (e.g. 'a@co.com,b@co.com').

Returns: JSON with total_added (always 0), total_removed, errors array.

Inputs: emails (required), list_id (required), segment_id (required), account. Returns: result

replicate_campaignA

Clone an existing campaign into a new draft with identical settings, recipients, and content.

Use to reuse a successful campaign as a starting point. Works on campaigns of any status (draft, scheduled, sent). The new campaign is created in 'save' (draft) status. Use update_campaign and set_campaign_content to modify the copy before sending. Use create_campaign instead to build from scratch.

Args: campaign_id: The campaign ID to replicate (e.g. 'abc123def4'). Obtain from list_campaigns.

Returns: JSON with fields: id (string, the NEW campaign's ID, different from original), status ('save'), title (original title with " (copy)" appended), web_id (int, for Mailchimp web UI).

Example: replicate_campaign(campaign_id="abc123") -> {"id": "def456", "status": "save", "title": "Spring Sale (copy)", "web_id": 789012}

Inputs: campaign_id (required), account. Returns: result

resend_to_non_openersA
Destructive

Create a new draft campaign targeting only recipients who did not open the original.

The new campaign inherits content and settings from the original. Not idempotent: calling twice creates two separate drafts. Workflow: resend_to_non_openers -> update_campaign (change subject) -> send_campaign or schedule_campaign. Do not use for A/B test campaigns or campaigns sent less than 24 hours ago (open tracking may be incomplete).

Returns error if the original campaign status is not 'sent'.

Args: campaign_id: ID of the original sent campaign (e.g. 'abc123def4'). Obtain from list_campaigns(status='sent').

Returns: JSON with id (new campaign ID), status ('save'), title, web_id.

Inputs: campaign_id (required), account. Returns: result

resume_rss_campaignA

Resume a paused RSS-driven campaign so it continues sending scheduled editions.

Use to restart an RSS campaign previously paused with pause_rss_campaign. Applies only to campaigns of type 'rss'. Use get_campaign_details to confirm the campaign type.

Args: campaign_id: RSS campaign ID to resume. Obtain from list_campaigns or search_campaigns.

Returns: JSON with the API response confirming the resume action, or an error if not an RSS campaign.

Inputs: campaign_id (required), account. Returns: result

schedule_campaignA

Schedule a campaign draft for sending at a specific future time.

Use to schedule delivery of a draft campaign. The campaign must have content set via set_campaign_content and be in 'save' status. Use unschedule_campaign to cancel a scheduled send. Use send_campaign instead for immediate delivery. Use send_test_email first to preview.

Args: campaign_id: The campaign ID (e.g. 'abc123def4'). Must be in 'save' status with content set. schedule_time: When to send. ISO 8601 datetime in UTC (e.g. '2025-06-15T14:00:00Z'). Must be at least 15 minutes in the future. Mailchimp rounds to the nearest quarter hour.

Returns: JSON with fields: status ("scheduled"), campaign_id, schedule_time. Returns error if campaign has no content or is not in draft status.

Example: schedule_campaign(campaign_id="abc123", schedule_time="2025-06-15T14:00:00Z") -> {"status": "scheduled", "campaign_id": "abc123", "schedule_time": "2025-06-15T14:00:00Z"}

Inputs: campaign_id (required), schedule_time (required), account. Returns: result

search_automation_campaignsA
Read-only

List campaigns originated by an automation or a Customer Journey (campaign type='automation').

Every email Mailchimp sends from a Classic automation or a Customer Journey creates a campaign object with type='automation'. This tool filters /campaigns to surface only those, so you can answer "what did my automations send recently?" without scanning all campaigns.

Use this as the most practical workaround for the lack of a public Customer Journeys read API: while you can't list the journeys themselves, you can list the campaigns they emit. Use list_automations for Classic-only metadata (journey internals aren't exposed). Use list_campaigns for the full campaign feed.

Args: count: Number of campaigns to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count. list_id: Optional audience ID to restrict to a single audience. Obtain from list_audiences. status: Filter by campaign status. Valid values: 'save', 'paused', 'schedule', 'sending', 'sent'. Omit for all. since_send_time: Only return campaigns sent after this ISO 8601 datetime (e.g. '2026-04-01T00:00:00Z'). before_send_time: Only return campaigns sent before this ISO 8601 datetime.

Returns: JSON with total_items and campaigns array. Each campaign: id, status, title, subject_line, send_time, emails_sent, list_id, list_name. Useful to compute automation send volume and identify which automation/journey produced which email (via title patterns).

Inputs: count, offset, status, account, +3 more. Returns: result

search_campaignsA
Read-only

Search campaigns by keyword across titles, subject lines, and list names.

Use to find campaigns when you do not know the ID. Use list_campaigns to browse by status or date instead. Queries under 3 characters return an error.

Args: query: Search string (minimum 3 characters). Matches against campaign titles, subject lines, and list names. count: Number of results to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and results array. Each result: campaign object with id, type, status, title, subject_line, send_time, emails_sent.

Inputs: query (required), count, offset, account. Returns: result

search_membersA
Read-only

Search for members across all audiences by email address or name, returning both exact and fuzzy matches.

Use when looking for a specific person and you may not know which audience they belong to. Use list_audience_members instead to browse all members of a known audience. Use get_member_activity or get_member_tags after finding a member for engagement data.

Args: query: Search query. Full email address for exact match, or name/partial email for fuzzy search. Minimum 3 characters. list_id: Optional audience/list ID to restrict search to a single audience. Obtain from list_audiences.

Returns: JSON with results array combining exact and fuzzy matches. Each result: email, status ('subscribed', 'unsubscribed', etc.), full_name, list_id (audience the member belongs to). Exact matches appear first.

Example: search_members(query="john@example.com") -> {"results": [{"email": "john@example.com", "status": "subscribed", "list_id": "abc123", ...}]}

Inputs: query (required), account, list_id. Returns: result

send_campaignA
Destructive

Send a campaign immediately to all targeted recipients. Emails begin delivering within minutes.

Use for immediate delivery. The campaign must have content set via set_campaign_content and be in 'save' (draft) status. Use schedule_campaign instead to send at a future time. Use send_test_email first to preview the email before sending to real recipients. Once sent, emails cannot be recalled.

Args: campaign_id: The campaign ID to send (e.g. 'abc123def4'). Must be in 'save' status with content set. Obtain from create_campaign or list_campaigns(status='save').

Returns: JSON with fields: status ("sent"), campaign_id. Returns error if the campaign has no content, is already sent, or is in schedule status (use unschedule_campaign first).

Example: send_campaign(campaign_id="abc123") -> {"status": "sent", "campaign_id": "abc123"}

Inputs: campaign_id (required), account. Returns: result

send_test_emailA

Send a test/preview email to specific addresses without affecting the real audience.

Side effect: sends a real email. Tests do not count against send limits and are not tracked in reports. Campaign must have content set via set_campaign_content. Recommended before send_campaign or schedule_campaign.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must have content set. test_emails: Comma-separated emails (e.g. 'me@co.com,team@co.com'). Max 10 per request. send_type: Format: 'html' (default) or 'plaintext'.

Returns: JSON with status ("test_sent"), campaign_id, test_emails array. Error if no content set.

Inputs: campaign_id (required), test_emails (required), account, send_type. Returns: result

set_campaign_contentA

Set the full HTML body of a campaign draft, replacing any existing content entirely.

Use after create_campaign to add the email body before sending. The campaign must be in 'save' (draft) status. Overwrites all previous content. Typical workflow: create_campaign -> set_campaign_content -> send_test_email -> send_campaign. Use update_campaign to change settings (subject, sender) instead of content.

Args: campaign_id: The campaign ID (e.g. 'abc123def4'). Obtain from create_campaign or list_campaigns(status='save'). html: Complete HTML content for the email body. Must be valid HTML. Use inline CSS for email client compatibility. Mailchimp merge tags (e.g. |FNAME|, |UNSUB|) are supported. Large HTML payloads may time out; keep under 200KB.

Returns: JSON with fields: status ("content_set"), campaign_id. Returns error if campaign is not in draft status.

Example: set_campaign_content(campaign_id="abc123", html="Hello |FNAME|!") -> {"status": "content_set", "campaign_id": "abc123"}

Inputs: html (required), campaign_id (required), account. Returns: result

start_automationA

Start or resume all emails in an automation workflow, activating delivery to queued subscribers.

Use to activate a new automation or resume a paused one. Queued subscribers begin receiving emails. Use pause_automation to temporarily stop. Use list_automations to check current status.

Args: automation_id: The automation workflow ID (e.g. 'auto123'). Obtain from list_automations.

Returns: JSON with fields: status ("started"), automation_id. Returns error if automation is already sending or is in draft status.

Example: start_automation(automation_id="auto123") -> {"status": "started", "automation_id": "auto123"}

Inputs: automation_id (required), account. Returns: result

start_automation_emailA

Start a specific email in a classic automation workflow.

Resumes sending for a single automation email that was previously paused. Queued subscribers begin receiving the email again according to the workflow schedule.

Args: workflow_id: The unique id of the classic automation workflow. workflow_email_id: The unique id of the automation email to start.

Returns: JSON confirming the start action.

Inputs: workflow_id (required), workflow_email_id (required), account. Returns: result

tag_memberA
Idempotent

Add or remove tags from a single member. Does not modify profile data or subscription status.

Tags are case-insensitive free-form labels. Added tags are created automatically if new; removed tags are silently ignored if not present. Idempotent. Choose the right member tool: tag_member for per-member tag changes, add_members_to_segment for bulk-adding members to a tag/segment, add_member with tags param for tagging at signup, update_member for profile/status changes, get_member_tags to check current tags.

Returns 404 error if the member does not exist.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the member. Must exist in the audience. tags_to_add: Comma-separated tag names to add (e.g. 'VIP,Returning Customer'). tags_to_remove: Comma-separated tag names to remove (e.g. 'Trial').

Returns: JSON with status ("updated"), email_address, tags array with name and status 'active'/'inactive'.

Inputs: list_id (required), email_address (required), account, tags_to_add, +1 more. Returns: result

trigger_customer_journeyA

Trigger a contact into a specific step of a Customer Journey workflow.

Side effect: the contact begins receiving journey emails immediately. The contact must be a subscribed member of the journey's audience. Use list_automations to find journey IDs. For Classic Automations, use start_automation instead. For one-time emails, use send_campaign or create_campaign instead.

Returns error if contact is not subscribed or step is not a valid API-trigger entry point.

Args: journey_id: Customer Journey ID. Found in the Mailchimp web UI or via list_automations. step_id: Step ID to trigger into. Must be an API-trigger entry point. email_address: Email of the contact. Must be subscribed in the journey's audience.

Returns: JSON with status ('triggered'), journey_id, step_id, email_address.

Inputs: step_id (required), journey_id (required), email_address (required), account. Returns: result

unpublish_landing_pageA

Take a published landing page offline. The public URL stops serving the page.

Reversible — re-publish with publish_landing_page. Use delete_landing_page for permanent removal instead.

Returns 404 error if page_id is invalid.

Args: page_id: Landing page ID to unpublish. Obtain from list_landing_pages.

Returns: JSON with status ('unpublished') and page_id on success.

Inputs: page_id (required), account. Returns: result

unpublish_surveyA

Unpublish a survey that is currently live, taking it offline.

Use list_surveys to find the survey_id and confirm it is published. Use publish_survey to put it back live.

Args: list_id: Audience/list ID (from list_audiences). survey_id: Survey ID (from list_surveys).

Returns: JSON with status 'unpublished' and the survey_id, or an error object.

Inputs: list_id (required), survey_id (required), account. Returns: result

unschedule_campaignA

Cancel a scheduled campaign send, returning it to draft ('save') status for editing.

Use to cancel a scheduled send before it goes out. Only works on campaigns in 'schedule' status; returns error for drafts or sent campaigns. After unscheduling, the campaign can be edited via update_campaign/set_campaign_content and rescheduled.

Args: campaign_id: The campaign ID to unschedule (e.g. 'abc123def4'). Must be in 'schedule' status. Obtain from list_campaigns(status='schedule').

Returns: JSON with fields: status ("unscheduled"), campaign_id. Returns error if the campaign is not currently scheduled.

Example: unschedule_campaign(campaign_id="abc123") -> {"status": "unscheduled", "campaign_id": "abc123"}

Inputs: campaign_id (required), account. Returns: result

unsubscribe_memberA

Unsubscribe a member from an audience, preserving profile and history for reporting.

Reversible via update_member(status='subscribed'). Use delete_member for permanent removal (GDPR). Returns 404 error if member does not exist.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the member. Must be a valid email address and exist in the audience.

Returns: JSON with email_address, status ("unsubscribed").

Inputs: list_id (required), email_address (required), account. Returns: result

update_audienceA

Update audience-level settings: name, default sender, subject, and permission reminder.

Changes apply to newly created campaigns only; does not retroactively affect existing ones. Only provided fields are updated. Use get_audience_details to check current settings.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. name: New audience display name (shown in Mailchimp UI and audience picker). from_name: Default sender name for new campaigns (e.g. 'Marketing Team'). Max 100 chars. from_email: Default sender email. Must be a verified sending domain in Mailchimp. subject: Default subject line for new campaigns (e.g. 'Monthly Update'). Max 150 chars. permission_reminder: Why subscribers receive emails (required by CAN-SPAM).

Returns: JSON with id, name, permission_reminder, campaign_defaults (from_name, from_email, subject, language).

Inputs: list_id (required), name, account, subject, +3 more. Returns: result

update_batch_webhookA

Update the target URL of an existing batch webhook.

Use to point an existing batch webhook at a new callback URL. Use list_batch_webhooks to find batch_webhook_id values and delete_batch_webhook to remove a webhook instead.

Returns 404 error if batch_webhook_id is invalid.

Args: batch_webhook_id: The batch webhook ID to update. Obtain from list_batch_webhooks. url: The new callback URL Mailchimp will POST to when a batch completes.

Returns: JSON with id, url, enabled (boolean). Returns an error object if the input is rejected.

Inputs: url (required), batch_webhook_id (required), account. Returns: result

update_campaignA

Update settings or segment targeting of an existing campaign draft.

Use to modify subject line, sender, or segment targeting before sending. Only works on campaigns in 'save' (draft) status; returns error for sent/scheduled campaigns. Only provided fields are updated; omitted fields remain unchanged. Use set_campaign_content to change the HTML body instead.

Args: campaign_id: The campaign ID to update (e.g. 'abc123def4'). Obtain from list_campaigns or create_campaign. subject_line: New subject line for the email. title: New internal title for organizing in Mailchimp. preview_text: New preview/preheader text. from_name: New sender name. reply_to: New reply-to email address. Must be a verified domain. list_id: Audience/list ID. Required when changing segment_id. Obtain from list_audiences. segment_id: Saved segment ID to target. Requires list_id to also be set. Obtain from list_segments.

Returns: JSON with fields: id, status, settings (full settings object), recipients (list_id, segment_opts).

Example: update_campaign(campaign_id="abc123", subject_line="Updated Subject") -> {"id": "abc123", "status": "save", "settings": {"subject_line": "Updated Subject", ...}}

Inputs: campaign_id (required), title, account, list_id, +5 more. Returns: result

update_campaign_feedbackA

Update the text of an existing campaign feedback comment.

Use to edit a previously left collaboration note. Use list_campaign_feedback to discover feedback IDs.

Args: campaign_id: Campaign ID the feedback belongs to. Obtain from list_campaigns. feedback_id: Feedback comment ID to update. Obtain from list_campaign_feedback. message: New comment text, replacing the previous message.

Returns: JSON with feedback_id, message, is_complete, block_id, updated_at.

Inputs: message (required), campaign_id (required), feedback_id (required), account. Returns: result

update_campaign_folderA

Rename an existing campaign folder.

Use to update a folder's display name; campaigns assigned to the folder are unaffected. Use list_campaign_folders to discover folder IDs.

Args: folder_id: Campaign folder ID to update. Obtain from list_campaign_folders. name: New display name for the folder.

Returns: JSON with id, name, and count of campaigns in the folder.

Inputs: name (required), folder_id (required), account. Returns: result

update_landing_pageA

Update settings of an existing landing page. Only provided fields are changed.

Cannot change list_id or template after creation; create a new page instead. Use publish_landing_page / unpublish_landing_page to change live status. Use get_landing_page to inspect current settings before updating.

Returns 404 error if page_id is invalid.

Args: page_id: Landing page ID. Obtain from list_landing_pages. name: New internal name. title: New browser tab title. description: New internal description. tracking_opens: Toggle open tracking on/off. tracking_clicks: Toggle click tracking on/off.

Returns: JSON with id, name, title, status, url, updated_at, list_id.

Inputs: page_id (required), name, title, account, +3 more. Returns: result

update_memberA
Idempotent

Update a member's profile fields or subscription status. Does not manage tags.

Only provided fields are updated; omitted fields remain unchanged. Idempotent: re-applying the same values is safe. Side effect: changing status to 'pending' triggers a re-confirmation email. Choose the right member tool: update_member for profile/status changes, tag_member for tag management, unsubscribe_member as shortcut for opt-out, add_member if the contact does not exist yet, batch_subscribe for bulk operations.

Returns 404 error if member does not exist. Returns 400 if status transition is invalid (e.g. cleaned to subscribed).

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: Email of the member to update. Must exist in the audience. status: New status: 'subscribed', 'unsubscribed', 'cleaned', 'pending'. first_name: New first name (FNAME merge field). last_name: New last name (LNAME merge field).

Returns: JSON with id, email_address, status, full_name.

Inputs: list_id (required), email_address (required), status, account, +2 more. Returns: result

update_member_noteA

Update the text of an existing member note. Replaces the entire note body.

Use list_member_notes to find note_ids. Use add_member_note instead to create a new note rather than overwriting; use delete_member_note to remove a note.

Returns 404 if the note or member does not exist.

Args: list_id: Audience/list ID. Obtain from list_audiences. email_address: Email of the member who owns the note. note_id: Note ID to update. Obtain from list_member_notes. note: New note text (max 1000 chars). Replaces the previous text entirely.

Returns: JSON with id, email_address, note (new value), updated_at.

Inputs: note (required), list_id (required), note_id (required), email_address (required), +1 more. Returns: result

update_merge_fieldA

Update a merge field's name, default value, required flag, or dropdown/radio choices.

Only provided fields are updated; omitted fields remain unchanged. Choices are replaced entirely (old choices are lost). Do not use to change field type or tag (immutable after creation); use delete_merge_field then create_merge_field instead.

Returns 404 error if merge_id is invalid or does not exist.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. merge_id: Merge field ID (numeric string, e.g. '5'). Obtain from list_merge_fields. name: New display name for the field. required: Whether the field is required when subscribing. default_value: New default value for new subscribers. choices: Comma-separated choices for dropdown/radio types (e.g. 'Small,Medium,Large'). Replaces all existing choices. Ignored for other field types.

Returns: JSON with merge_id, tag, name, type, required.

Inputs: list_id (required), merge_id (required), name, account, +3 more. Returns: result

update_promo_codeA

Update a promo code's string, redemption URL, or enabled state. Cannot move a code to a different rule — delete and re-create instead.

Common use: toggle enabled=false to temporarily disable a code after a campaign ends, without deleting the redemption history.

Returns 404 if any of store_id, promo_rule_id, or promo_code_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Rule ID the code is attached to. promo_code_id: Code ID to update. code: New code string (case-insensitive). redemption_url: New redemption URL. enabled: Toggle the code on/off.

Returns: JSON with id, code, redemption_url, enabled, updated_at.

Inputs: store_id (required), promo_code_id (required), promo_rule_id (required), code, +3 more. Returns: result

update_promo_ruleA

Update an existing promo rule. Only provided fields are changed.

Useful to toggle a rule on/off (enabled), extend an end date, or adjust the discount amount mid-campaign. Use list_promo_rules to discover promo_rule_ids.

Returns 404 if store_id or promo_rule_id is invalid.

Args: store_id: E-commerce store ID. promo_rule_id: Existing rule ID. description: New internal description. amount: New discount amount. type: New type ('fixed' or 'percentage'). target: New target ('per_item', 'total', or 'shipping'). enabled: Toggle the rule on/off. title: New public title. starts_at: New start datetime (ISO 8601). ends_at: New end datetime (ISO 8601).

Returns: JSON with id, title, description, amount, type, target, enabled, updated_at.

Inputs: store_id (required), promo_rule_id (required), type, title, +7 more. Returns: result

update_segmentA
Idempotent

Update a segment's name or dynamic filter conditions.

Only provided fields are updated. Idempotent: re-applying the same name is safe. Cannot change a segment from static to dynamic or vice versa. Use add_members_to_segment or remove_members_from_segment to manage static segment membership instead.

Returns 404 error if segment_id is invalid. Providing match without conditions_json is ignored.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. segment_id: Segment ID to update (numeric string, e.g. '12345'). Obtain from list_segments. name: New display name for the segment. match: Condition match type for dynamic segments: 'all' (AND) or 'any' (OR). Must be provided together with conditions_json. conditions_json: JSON string of conditions array. Must be provided with match.

Returns: JSON with id, name, member_count, type ('static'/'saved'), options.

Inputs: list_id (required), segment_id (required), name, match, +2 more. Returns: result

update_storeA

Update an existing e-commerce store's name, currency, connected audience, or metadata.

Only fields supplied in additional_fields are changed. Many stores sync automatically via Shopify or WooCommerce integrations; these manual writes suit custom or headless storefronts.

Args: store_id: E-commerce store ID. additional_fields: Dict of documented fields to update (e.g. name, currency_code, domain, email_address, primary_locale, timezone) merged into the request body.

Returns: JSON with the updated store object.

Inputs: store_id (required), account, additional_fields. Returns: result

update_store_cartA

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.

Inputs: cart_id (required), store_id (required), account, tax_total, +4 more. Returns: result

update_store_customerA

Update an existing store customer's name, opt-in status, address, or company.

Only fields supplied in additional_fields are changed. 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: Existing customer ID. additional_fields: Dict of documented fields to update (e.g. opt_in_status, first_name, last_name, company, address) merged into the request body.

Returns: JSON with the updated customer object.

Inputs: store_id (required), customer_id (required), account, additional_fields. Returns: result

update_store_orderA

Update an existing e-commerce order's fields.

Only the fields you pass in additional_fields are changed; omit a field to leave it untouched. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync orders automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Existing order ID within the store. additional_fields: Optional dict of order fields to update, merged into the body (e.g. financial_status, fulfillment_status, order_total, shipping_total, currency_code).

Returns: JSON with the updated order object.

Inputs: order_id (required), store_id (required), account, additional_fields. Returns: result

update_store_order_lineA

Update a line item on an existing e-commerce order.

Only the fields you pass in additional_fields are changed; omit a field to leave it untouched. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync order lines automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. order_id: Order ID that owns the line. line_id: Existing line item ID to update. additional_fields: Optional dict of line fields to update, merged into the body (e.g. product_id, product_variant_id, quantity, price, discount).

Returns: JSON with the updated line object.

Inputs: line_id (required), order_id (required), store_id (required), account, +1 more. Returns: result

update_store_productA

Update an existing product's title, description, images, or other metadata.

Only fields supplied in additional_fields are changed. Many stores sync products automatically via Shopify or WooCommerce integrations; these manual writes suit custom or headless storefronts.

Args: store_id: E-commerce store ID. product_id: Existing product ID. additional_fields: Dict of documented fields to update (e.g. title, handle, url, description, type, vendor, image_url) merged into the request body.

Returns: JSON with the updated product object.

Inputs: store_id (required), product_id (required), account, additional_fields. Returns: result

update_store_product_imageA

Update an image attached to a product in an e-commerce store.

Only the fields you pass in additional_fields are changed; omit a field to leave it untouched. Manual commerce writes suit custom/headless stores; Shopify and WooCommerce integrations sync product images automatically.

Args: store_id: E-commerce store ID. Obtain from list_ecommerce_stores. product_id: Product ID that owns the image. image_id: Existing image ID to update. additional_fields: Optional dict of image fields to update, merged into the body (e.g. url, variant_ids).

Returns: JSON with the updated image object.

Inputs: image_id (required), store_id (required), product_id (required), account, +1 more. Returns: result

update_store_product_variantA

Update an existing product variant's price, SKU, inventory, or other attributes.

Only fields supplied in additional_fields are changed. Many stores sync variants automatically via Shopify or WooCommerce integrations; these manual writes suit custom or headless storefronts.

Args: store_id: E-commerce store ID. product_id: Product ID that owns the variant. variant_id: Existing variant ID. additional_fields: Dict of documented fields to update (e.g. title, url, sku, price, inventory_quantity, image_url) merged into the request body.

Returns: JSON with the updated variant object.

Inputs: store_id (required), product_id (required), variant_id (required), account, +1 more. Returns: result

update_templateA

Update an existing template's name or HTML content.

Only provided fields are updated. Only works for user-created templates; gallery and base templates cannot be modified. Use create_template to create a new template instead of modifying a gallery template.

Returns 404 error if template_id is invalid.

Args: template_id: Template ID to update (numeric string, e.g. '12345'). Obtain from list_templates. name: New display name for the template. html: New HTML content. Replaces all existing content.

Returns: JSON with id, name, type, active, date_edited.

Inputs: template_id (required), html, name, account. Returns: result

update_template_folderA

Rename an existing template folder.

Use to update a folder's display name; templates assigned to the folder are unaffected. Use list_template_folders to discover folder IDs.

Args: folder_id: Template folder ID to update. Obtain from list_template_folders. name: New display name for the folder.

Returns: JSON with id, name, and count of templates in the folder.

Inputs: name (required), folder_id (required), account. Returns: result

upload_fileA

Upload a new image or file to the File Manager (base64-encoded).

Enables programmatic image hosting for campaign and template content: upload here, then reference the returned full_size_url in your HTML. Use list_file_folders to target a folder, list_files to browse existing files, and delete_file to remove one.

Args: name: File name including extension (e.g. 'hero.png'). Shown in the File Manager. file_data: The file content, base64-encoded (not a URL or raw bytes). folder_id: Optional folder ID (from list_file_folders) to upload into. Omit for the root.

Returns: JSON with id (use as file_id), name, type, full_size_url (hosted URL for embedding), thumbnail_url, size, width, height, folder_id, created_at.

Inputs: name (required), file_data (required), account, folder_id. Returns: result

upsert_memberA
Idempotent

Add a member to an audience or update them if they already exist (idempotent upsert).

Use to reliably add-or-update a member in a single call without checking for existence first. Use add_member to strictly create a new member, or update_member to only modify an existing one.

Args: list_id: Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences. email_address: The member's email address. The subscriber hash is derived automatically. status_if_new: Status to apply only when the member is newly created (default 'subscribed'). Valid: 'subscribed', 'unsubscribed', 'cleaned', 'pending', 'transactional'. merge_fields: Optional dict of merge field values (e.g. {'FNAME': 'Ada', 'LNAME': 'Lovelace'}). tags: Optional list of tag names to apply to the member.

Returns: JSON with id, email_address, status, merge_fields, tags, list_id, and timestamps. Returns an error object if the input is rejected.

Inputs: list_id (required), email_address (required), tags, account, +2 more. Returns: result

verify_connected_site_scriptA

Verify that the Mailchimp tracking script is correctly installed on a connected site.

Run after installing the script returned by create_connected_site to confirm Mailchimp can detect it. Use get_connected_site to check the current installation status instead.

Args: connected_site_id: The connected site ID to verify. Obtain from list_connected_sites.

Returns: JSON with the connected site record reflecting the updated script installation status.

Inputs: connected_site_id (required), account. Returns: result

verify_verified_domainA

Complete domain verification by submitting the code emailed to the verification address.

Run create_verified_domain first to trigger the email, then pass the received code here. Once verified, the domain can authenticate and be used as a sending address.

Args: domain_name: The sending domain being verified (e.g. 'mail.example.com'). Obtain from list_verified_domains. code: The verification code emailed to the address from create_verified_domain.

Returns: JSON with domain, verified (boolean), authenticated (boolean), verification_status, authentication_status.

Inputs: code (required), domain_name (required), account. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 227 tools

    Disambiguation3/5

    Despite detailed descriptions, the sheer volume of 227 tools creates overlap and confusion. For example, multiple member tools (add_member, upsert_member, batch_subscribe) and equivalent delete operations (delete_member, delete_member_permanent) make it difficult for an agent to select the correct one without careful reading.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (e.g., create_campaign, list_audiences), but there are minor inconsistencies such as 'upsert_member', 'ping', 'describe_tools', and multi-word verbs like 'resend_to_non_openers'.

    Tool Count1/5

    With 227 tools, the server is massively over-scoped. The recommended range is 3-15; 227 is an extreme mismatch, making navigation and selection impractical for agents.

    Completeness5/5

    The tool set covers nearly every aspect of the Mailchimp API: audiences, members, campaigns, automations, e-commerce, templates, landing pages, surveys, file manager, and more. It includes full CRUD lifecycle operations with no obvious gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to Mailchimp's Marketing API for comprehensive email marketing data retrieval.
      38
      99 npm
      12
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that interfaces with the Mailchimp Marketing API to manage audiences, email campaigns, and subscribers. It enables users to create and schedule campaigns, handle member lists, and send test or live emails through natural language commands.
      13
      31 npm
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A production-grade MCP server that integrates with the Mailchimp Marketing API to manage campaigns, audiences, members, and reports. It provides 28 specialized tools for automating marketing tasks such as sending emails, managing subscriber tags, and analyzing performance data.
      71
      1
      MIT