Skip to main content
Glama
damientilman

Mailchimp MCP

set_campaign_content

Set the full HTML body of a draft campaign, replacing existing content. Use after creating the campaign to add the email body before sending.

Instructions

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.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). Respects read-only and dry-run modes.

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"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
htmlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: replaces content entirely, requires draft status, authenticates via API key, subject to rate limits (10 concurrent), respects read-only/dry-run modes, and error handling for non-draft campaigns. Comprehensive for a mutation tool.

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?

Well-structured with purposeful sentences: main action, workflow, behavioral notes, parameter details, return spec, example. No redundant information; every sentence earns its place. Front-loaded with essential purpose.

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 two required parameters and no output schema, the description covers input constraints, output format, workflow integration, and error conditions. Complete for a content-setting tool with sibling differentiation.

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 coverage is 0%, but description adds rich semantics: campaign_id source (create_campaign/list_campaigns), html requirements (valid HTML, inline CSS, merge tags, 200KB limit). Compensates fully for schema gaps.

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 sets the full HTML body of a campaign draft, replacing existing content. It distinguishes from sibling tools like update_campaign for settings, providing specific verb+resource 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?

Provides explicit workflow (create_campaign -> set_campaign_content -> send_test_email -> send_campaign), states campaign must be in 'save' status, and directs when to use update_campaign instead. Offers clear when-to-use and when-not-to-use guidance.

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