Skip to main content
Glama

get_campaign

Retrieve comprehensive campaign details including settings, tracking, and recipient information from Mailchimp to analyze performance and manage marketing activities.

Instructions

Get full details for a specific campaign including settings, tracking, and recipient info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the get_campaign MCP tool. It fetches campaign details from the Mailchimp API and formats the relevant data.
    @mcp.tool()
    async def get_campaign(campaign_id: str) -> str:
        """Get full details for a specific campaign including settings, tracking, and recipient info."""
        mc = get_client()
        c = await mc.get(f"/campaigns/{campaign_id}")
        s = c.get("settings", {})
        r = c.get("recipients", {})
        t = c.get("tracking", {})
        return _fmt({
            "id": c["id"],
            "type": c.get("type", ""),
            "status": c.get("status", ""),
            "title": s.get("title", ""),
            "subject_line": s.get("subject_line", ""),
            "preview_text": s.get("preview_text", ""),
            "from_name": s.get("from_name", ""),
            "reply_to": s.get("reply_to", ""),
            "list_id": r.get("list_id", ""),
            "list_name": r.get("list_name", ""),
            "recipient_count": r.get("recipient_count", 0),
            "send_time": c.get("send_time"),
            "emails_sent": c.get("emails_sent", 0),
            "opens_tracking": t.get("opens", False),
            "clicks_tracking": t.get("html_clicks", False),
            "created_at": c.get("create_time", ""),
        })
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool retrieves details, implying a read-only operation, but does not specify if it requires authentication, has rate limits, or what the output format entails. While the presence of an output schema might mitigate some gaps, the description itself lacks essential behavioral context for safe and effective use.

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 front-loads the key action ('Get full details') and specifies the scope ('including settings, tracking, and recipient info'). There is no wasted language, and it is appropriately sized for the tool's complexity.

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's moderate complexity (1 parameter, no annotations, but with an output schema), the description is minimally adequate. It covers the purpose but lacks usage guidelines and detailed behavioral context. The output schema existence reduces the need to explain return values, but the description should do more to guide the agent in tool selection and invocation, especially with many sibling tools available.

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?

The input schema has 1 parameter with 0% description coverage, so the schema provides no semantic information. The description does not explicitly mention the 'campaign_id' parameter, but it implies the need for a specific campaign by stating 'for a specific campaign'. This adds some meaning beyond the schema, though it could be more direct. With 0% coverage, the description partially compensates, warranting a score above baseline.

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 'campaign' with specific details ('full details including settings, tracking, and recipient info'), making the purpose explicit. However, it does not distinguish this tool from sibling tools like 'get_campaign_content' or 'get_campaign_report', which also retrieve campaign-related information but focus on specific aspects, so it lacks sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'get_campaign_content' or 'get_campaign_report', nor does it mention prerequisites like requiring a campaign ID. It implies usage for retrieving campaign details but offers no explicit context or exclusions, leaving the agent to infer from the tool name alone.

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