Skip to main content
Glama
damientilman

Mailchimp MCP

get_campaign_details

Retrieve the full configuration of any Mailchimp campaign, including subject line, sender, audience targeting, and tracking settings.

Instructions

Retrieve full configuration of a specific campaign including settings, recipients, and tracking options.

Use to inspect subject line, sender, audience targeting, or tracking settings. Use get_campaign_report instead for post-send performance (opens, clicks, bounces). 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.

Returns: JSON with fields: id, type, status, settings (subject_line, title, from_name, reply_to), recipients (list_id, segment_opts), send_time (ISO 8601 or null), emails_sent, tracking (opens, html_clicks, text_clicks booleans). Returns error if campaign_id is invalid.

Example: get_campaign_details(campaign_id="abc123def4") -> {"id": "abc123def4", "status": "sent", "settings": {"subject_line": "Spring Sale", ...}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description notes authentication via API key, subject to Mailchimp API rate limits (max 10 concurrent requests), and that it is read-only and safe to retry. No annotations are provided, so the description fully covers behavioral context.

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 sections for purpose, usage, auth, args, returns, 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?

The description includes expected return fields and an example. Given an output schema exists (not shown but indicated), the description is complete for this read-only tool with one parameter.

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?

With 0% schema description coverage, the description fully compensates by explaining the campaign_id parameter: it is the Mailchimp campaign ID (e.g., 'abc123def4'), obtainable from list_campaigns or search_campaigns.

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 retrieves full configuration of a specific campaign, including settings, recipients, and tracking options. It distinguishes itself from siblings like get_campaign_report and list_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 this tool (inspect subject line, sender, audience, tracking) and when to use alternatives (get_campaign_report for performance). It also mentions obtaining campaign IDs from list_campaigns or search_campaigns.

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