Skip to main content
Glama
damientilman

Mailchimp MCP

update_audience

Update audience-level settings: name, default sender, subject, and permission reminder. Applies to new campaigns only.

Instructions

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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
accountNo
list_idYes
subjectNo
from_nameNo
from_emailNo
permission_reminderNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description adds critical behavioral traits: changes apply only to newly created campaigns (no retroactive effect) and only provided fields are updated (partial update). This provides valuable context that annotations alone cannot convey.

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

Conciseness5/5

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

The description is brief yet comprehensive, front-loading the purpose and behavioral notes, then listing parameters with clear explanations and a Returns section. Every sentence adds value, avoiding redundancy or fluff. The structure is easy to parse.

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 the tool has 7 parameters (1 required) and an output schema (though not detailed in context description), the description covers the key behavior (partial update, effect on new campaigns) and parameter semantics thoroughly. It also references a related tool (get_audience_details) for completeness. For a moderately complex update tool, this is fully adequate.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description explains each parameter in detail: list_id format and source, length limits for subject, verification requirement for from_email, and explains permission_reminder as required by CAN-SPAM. This adds substantial meaning beyond the schema, fully compensating for the lack of 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?

The description clearly states the tool updates audience-level settings (name, default sender, subject, permission reminder) and distinguishes between updating audience settings versus checking them (get_audience_details). It also clarifies the scope (affects only new campaigns), making the purpose very specific and distinct from sibling tools like update_campaign.

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

Usage Guidelines4/5

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

The description provides guidance on when to use this tool by suggesting to use get_audience_details to check current settings first. It implies this tool is for updating settings, not for reading. However, it does not explicitly list when not to use it or direct to alternatives for other types of updates (e.g., campaign-level settings), which prevents a perfect score.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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

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

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