Skip to main content
Glama
damientilman

Mailchimp MCP

get_campaign_content

Retrieve the plain text and optionally HTML body of a sent Mailchimp campaign for content audits, analysis, or repurposing.

Instructions

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.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). Read-only, safe to retry.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes
include_htmlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description discloses authentication ('Authenticated via API key'), rate limits ('max 10 concurrent requests'), read-only safety ('safe to retry'), error cases ('invalid campaign_id or no content'), and output details including variations for A/B campaigns. No annotations provided, so description carries full burden and does so thoroughly.

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 a front-loaded purpose, followed by usage guidelines, authentication/rate limits, parameter details, output description, and an example. Every sentence adds value without redundancy.

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's simplicity (2 params, no enums, has output schema), the description covers purpose, usage guidance, authentication, rate limits, parameter semantics, output format (including A/B variations), error handling, and an example. This is highly complete.

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 the description explains both parameters in detail: campaign_id provides example, source, and distinction from web_id; include_html explains purpose, default, and compactness benefit. This adds significant meaning beyond the schema.

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 'Read the rendered body copy of a campaign (plain text, optionally HTML).' It uses a specific verb and resource, and distinguishes from siblings like get_campaign_details, get_campaign_report, list_campaigns, and search_campaigns.

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?

The description explicitly says when to use ('for content audits, analysis, or repurposing'), and provides alternatives: 'Use get_campaign_details for settings/metadata... get_campaign_report for post-send performance. Use list_campaigns or search_campaigns to find campaign IDs.'

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