Skip to main content
Glama
dazanza
by dazanza

list_campaigns

Retrieve and filter recent Mailchimp campaigns by status to monitor email marketing performance and track campaign progress.

Instructions

List recent Mailchimp campaigns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of results (default 10)
statusNoFilter by status: save, paused, schedule, sending, sent

Implementation Reference

  • server.js:66-90 (handler)
    Tool registration and handler implementation for "list_campaigns" in server.js. It fetches recent Mailchimp campaigns using the mailchimp SDK and formats the response for the MCP client.
    // --- Tool 3: List Campaigns ---
    server.tool(
      "list_campaigns",
      "List recent Mailchimp campaigns.",
      {
        count: z.number().optional().describe("Number of results (default 10)"),
        status: z.string().optional().describe("Filter by status: save, paused, schedule, sending, sent"),
      },
      async ({ count, status }) => {
        const opts = { count: count || 10 };
        if (status) opts.status = status;
        const response = await mailchimp.campaigns.list(opts);
        const campaigns = response.campaigns.map((c) => ({
          id: c.id,
          type: c.type,
          status: c.status,
          subject_line: c.settings?.subject_line,
          from_name: c.settings?.from_name,
          send_time: c.send_time,
          emails_sent: c.emails_sent,
          recipients: { list_id: c.recipients?.list_id, list_name: c.recipients?.list_name },
        }));
        return { content: [{ type: "text", text: JSON.stringify(campaigns, null, 2) }] };
      }
    );
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. While 'List' implies a read-only operation, it doesn't explicitly state whether this is safe, whether it requires authentication, what rate limits apply, or what happens with errors. The description mentions 'recent' campaigns but doesn't define what 'recent' means or if there are time-based limitations.

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 at just 4 words, with zero wasted language. It's front-loaded with the core purpose and includes the scope modifier 'recent' as the only additional detail. Every word earns its place, making this highly efficient communication.

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

Completeness2/5

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

For a read operation with 2 parameters and no output schema, the description is insufficiently complete. It doesn't explain what information is returned about campaigns, whether results are paginated, what 'recent' means operationally, or any error conditions. Without annotations or output schema, the description should provide more context about the tool's behavior and results.

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 input schema has 100% description coverage, with clear documentation for both 'count' (default 10) and 'status' (filter options). The description adds no additional parameter information beyond what's already in the schema. This meets the baseline expectation when schema coverage is high, but doesn't provide extra value like explaining parameter interactions or edge cases.

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 action ('List') and resource ('Mailchimp campaigns'), making the purpose immediately understandable. It specifies 'recent' campaigns, which adds useful scope information. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_campaign' or 'list_audiences' 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 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. It doesn't mention when to choose 'list_campaigns' over 'get_campaign' (for individual details) or 'list_audiences' (for different resources). There's also no information about prerequisites, dependencies, or typical use cases for listing 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/dazanza/mailchimp-mcp'

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