Skip to main content
Glama

get_campaign_content

Retrieve HTML and plain-text content from a Mailchimp campaign to review, edit, or repurpose email marketing materials.

Instructions

Get the HTML and plain-text content of a campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the get_campaign_content MCP tool, which retrieves and formats campaign content from the Mailchimp API.
    @mcp.tool()
    async def get_campaign_content(campaign_id: str) -> str:
        """Get the HTML and plain-text content of a campaign."""
        mc = get_client()
        data = await mc.get(f"/campaigns/{campaign_id}/content")
        return _fmt({
            "campaign_id": campaign_id,
            "plain_text": data.get("plain_text", "")[:2000],
            "html_preview": data.get("html", "")[:3000],
            "archive_html": data.get("archive_html", "")[:500],
        })
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read-only operation ('Get'), but doesn't mention any behavioral traits like permissions required, rate limits, error handling, or what the output contains beyond 'HTML and plain-text content'. This leaves significant gaps for an agent to understand how to use it effectively.

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 a single, efficient sentence that directly states the tool's function without any unnecessary words. It's front-loaded with the core action, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool has an output schema, the description doesn't need to explain return values, which helps. However, with no annotations and a simple but undocumented parameter, the description is minimal and lacks context about usage, behavior, or parameter details. It's adequate for a basic read operation but leaves room for improvement in guiding the agent.

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

Parameters3/5

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

The schema description coverage is 0%, so the description must compensate, but it doesn't add any meaning beyond what the input schema provides. The schema already indicates a required 'campaign_id' parameter, and the description doesn't explain what a campaign ID is, how to obtain it, or any formatting constraints. Since there's only one parameter, the baseline is 4, but the lack of additional semantic context reduces the score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('HTML and plain-text content of a campaign'), making the purpose specific and understandable. However, it doesn't distinguish this from sibling tools like 'get_campaign' or 'get_campaign_report', which might retrieve different campaign-related information.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this should be used instead of 'get_campaign' for content retrieval or clarify any prerequisites, such as needing a campaign ID from another operation.

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/AlexlaGuardia/mcp-mailchimp'

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