Skip to main content
Glama

get_campaign_report

Retrieve performance metrics for sent email campaigns including opens, clicks, bounces, and unsubscribes to analyze marketing effectiveness.

Instructions

Get performance report for a sent campaign — opens, clicks, bounces, unsubscribes, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The handler function `get_campaign_report` for retrieving campaign performance statistics using the Mailchimp API. It is decorated with `@mcp.tool()` for MCP registration.
    @mcp.tool()
    async def get_campaign_report(campaign_id: str) -> str:
        """Get performance report for a sent campaign — opens, clicks, bounces, unsubscribes, and more."""
        mc = get_client()
        r = await mc.get(f"/reports/{campaign_id}")
        return _fmt({
            "campaign_id": campaign_id,
            "subject_line": r.get("subject_line", ""),
            "emails_sent": r.get("emails_sent", 0),
            "opens": {
                "total": r.get("opens", {}).get("opens_total", 0),
                "unique": r.get("opens", {}).get("unique_opens", 0),
                "rate": r.get("opens", {}).get("open_rate", 0),
            },
            "clicks": {
                "total": r.get("clicks", {}).get("clicks_total", 0),
                "unique": r.get("clicks", {}).get("unique_clicks", 0),
                "rate": r.get("clicks", {}).get("click_rate", 0),
            },
            "bounces": {
                "hard": r.get("bounces", {}).get("hard_bounces", 0),
                "soft": r.get("bounces", {}).get("soft_bounces", 0),
            },
            "unsubscribes": r.get("unsubscribed", 0),
            "abuse_reports": r.get("abuse_reports", 0),
            "send_time": r.get("send_time", ""),
        })
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't mention whether this is a read-only operation (implied by 'Get'), permission requirements, rate limits, or what 'and more' entails. The description is minimal and doesn't adequately compensate for missing annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that efficiently conveys the core purpose. However, 'and more' is vague and could be tightened. The structure is front-loaded with the main action but lacks elaboration where needed.

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 1 parameter with 0% schema coverage and an output schema exists, the description is minimally adequate but incomplete. It covers the what but not the how or constraints. The output schema may detail return values, but the description doesn't prepare the agent for behavioral aspects like error handling or data freshness.

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?

Schema description coverage is 0%, so the description must compensate. It mentions 'for a sent campaign' which contextualizes the campaign_id parameter, but doesn't specify format, source, or validation rules. This adds some meaning beyond the bare schema but is insufficient for full parameter understanding.

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 'performance report for a sent campaign', specifying the type of data retrieved (opens, clicks, etc.). It distinguishes from siblings like get_campaign (likely basic metadata) and specific metric reports (get_click_report, get_open_report), but doesn't explicitly name alternatives.

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 on when to use this tool versus alternatives like get_campaign (for basic info) or get_click_report/get_open_report (for specific metrics). The description implies it's for comprehensive campaign performance data but doesn't provide explicit usage context or exclusions.

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