Skip to main content
Glama
damientilman

Mailchimp MCP

set_campaign_content

Set the full HTML body of a campaign draft, replacing any existing content. Use after creating a campaign to add email content 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.

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
htmlYes
accountNo
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description adds valuable behavioral context beyond annotations, such as campaign status requirement, overwriting behavior, size limit, and merge tag support. However, there is a contradiction: the description says it overwrites content (destructive), but annotations have destructiveHint=false. This inconsistency reduces reliability.

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 well-structured with separate sections for purpose, workflow, args, returns, and example. It is concise, front-loaded with the main purpose, and every sentence adds value.

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

Completeness4/5

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

Given the schema coverage is 0% and there is an output schema, the description covers most necessary information: purpose, parameters (2 of 3), return format, and usage context. The only gap is the lack of explanation for the account parameter, but it is optional.

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

Parameters4/5

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

With 0% schema description coverage, the description compensates by explaining campaign_id and html parameters in detail, including format, constraints, and examples. The optional account parameter is not described, but it's minor.

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 'Set the full HTML body of a campaign draft, replacing any existing content entirely.' It uses a specific verb and resource, and distinguishes from sibling tools like update_campaign (for settings) and create_campaign (for creation).

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 provides a workflow (create_campaign -> set_campaign_content -> send_test_email -> send_campaign) and contrasts with update_campaign for settings, giving clear guidance on when to use this tool vs alternatives.

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