Skip to main content
Glama
damientilman

Mailchimp MCP

create_audience

Create a new audience (list) in Mailchimp with required contact fields, campaign defaults, and CAN-SPAM-compliant permission reminder.

Instructions

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipYes
cityYes
nameYes
phoneNo
stateYes
accountNo
companyYes
countryYes
subjectYes
address1Yes
address2No
languageYes
from_nameYes
from_emailYes
email_type_optionNo
permission_reminderYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses side effect of creating a billable audience, error conditions, and return values. Annotations are minimal but consistent; description adds substantial behavioral context beyond annotations.

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

Conciseness4/5

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

Well-structured with purpose, side effect, error info, args list, and returns. Front-loaded with key info. Slightly verbose but necessary details; could be more concise but still clear.

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

Completeness5/5

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

Given 16 parameters (12 required), description covers all params, errors, return values, side effects, and sibling tools. No gaps for an AI agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, but description provides detailed explanations for all 16 parameters, including constraints (max length, format) and defaults, fully compensating for missing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states 'Create a new audience (list)' and distinguishes from siblings like update_audience, delete_audience, and list_audiences, providing specific verb+resource and differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use (create), mentions side effect (billable), error condition (400 if missing fields or plan limit), and names alternatives (update_audience, delete_audience, list_audiences) for different needs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/damientilman/mailchimp-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server