Skip to main content
Glama

list_campaigns

Retrieve email campaigns from Mailchimp with filtering options by status or audience list to manage marketing communications.

Instructions

List email campaigns. Filter by status (save, paused, schedule, sending, sent) or audience list_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
list_idNo
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Implementation of the 'list_campaigns' MCP tool. It fetches campaign data from the Mailchimp API, filters based on optional parameters, formats the result, and returns it as an MCP tool response.
    @mcp.tool()
    async def list_campaigns(
        status: str = "",
        list_id: str = "",
        count: int = 20,
        offset: int = 0,
    ) -> str:
        """List email campaigns. Filter by status (save, paused, schedule, sending, sent) or audience list_id."""
        mc = get_client()
        params: dict[str, Any] = {"count": min(count, 100), "offset": offset}
        if status:
            params["status"] = status
        if list_id:
            params["list_id"] = list_id
        data = await mc.get("/campaigns", params=params)
        campaigns = []
        for c in data.get("campaigns", []):
            s = c.get("settings", {})
            campaigns.append({
                "id": c["id"],
                "title": s.get("title", ""),
                "subject_line": s.get("subject_line", ""),
                "status": c.get("status", ""),
                "type": c.get("type", ""),
                "send_time": c.get("send_time"),
                "emails_sent": c.get("emails_sent", 0),
            })
        return _fmt({"total_items": data.get("total_items", 0), "campaigns": campaigns})
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 mentions filtering capabilities but lacks critical details: it doesn't specify whether this is a read-only operation, if it requires authentication, what the default sorting or pagination behavior is (though parameters suggest pagination), or potential rate limits. The description is minimal and misses key behavioral traits for a listing tool.

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 extremely concise—just one sentence—with zero wasted words. It front-loads the core purpose ('List email campaigns') and efficiently adds filtering details. Every part of the sentence earns its place by providing essential information without redundancy.

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

Completeness4/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 (4 parameters, no annotations, but with an output schema), the description is reasonably complete for a listing operation. The output schema likely handles return values, reducing the need for detailed output explanations. However, it lacks behavioral context (e.g., pagination defaults, error handling), which slightly limits completeness for an agent's effective use.

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 schema provides no parameter descriptions. The description adds some value by mentioning 'status' and 'list_id' as filtering options, including status values like 'save, paused, schedule, sending, sent'. However, it doesn't explain 'count' or 'offset' parameters, leaving half the parameters undocumented. This partial compensation results in a baseline 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 ('List') and resource ('email campaigns'), making the purpose immediately understandable. It distinguishes this tool from other campaign-related tools like 'get_campaign' or 'create_campaign' by focusing on listing multiple campaigns. However, it doesn't explicitly differentiate from other list tools like 'list_audiences' or 'list_templates' beyond the resource type.

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

Usage Guidelines3/5

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

The description implies usage by mentioning filtering options ('Filter by status or audience list_id'), which suggests when to use this tool for filtered listings. However, it doesn't provide explicit guidance on when to choose this over alternatives like 'get_campaign' (for single campaigns) or 'search_members' (for member-related queries), nor does it mention prerequisites 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