Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

list_campaign_reports

Retrieve all campaign performance reports from Mailchimp to analyze email marketing results and track engagement metrics.

Instructions

List all campaign reports

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the 'list_campaign_reports' tool within the handleToolCall switch statement. It invokes the service method and formats the response as JSON.
    case "list_campaign_reports":
      const campaignReports = await service.listCampaignReports();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              campaignReports.reports.map((r) => ({
                id: r.id,
                campaign_title: r.campaign_title,
                type: r.type,
                emails_sent: r.emails_sent,
                send_time: r.send_time,
                opens: r.opens,
                clicks: r.clicks,
              })),
              null,
              2
            ),
          },
        ],
      };
  • The service method listCampaignReports that performs the actual API call to fetch paginated campaign reports from Mailchimp's /reports endpoint.
    async listCampaignReports(): Promise<{ reports: MailchimpCampaignReport[] }> {
      return await this.makePaginatedRequest("/reports", "send_time", "DESC");
    }
  • Tool registration in getToolDefinitions array, including name, description, and input schema (no required parameters).
    {
      name: "list_campaign_reports",
      description: "List all campaign reports",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Input schema for the list_campaign_reports tool, defining an empty object with no properties or requirements.
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('List') but doesn't disclose behavioral traits such as pagination, sorting, filtering capabilities, rate limits, authentication needs, or what 'all' entails (e.g., date ranges, statuses). This leaves significant gaps 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 with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. This is an example of optimal conciseness for a simple tool.

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?

Given the complexity of listing operations (often involving pagination, filters, or sorting), no annotations, no output schema, and siblings that could confuse selection, the description is incomplete. It doesn't address behavioral aspects or usage context, making it inadequate for reliable agent operation.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied as it adequately handles the lack of parameters without introducing confusion.

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

Purpose3/5

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

The description 'List all campaign reports' clearly states the verb ('List') and resource ('campaign reports'), making the purpose understandable. However, it lacks specificity about scope or format, and doesn't differentiate from sibling tools like 'get_campaign_report' or 'list_campaigns', which could cause confusion about when to use each.

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. With siblings like 'get_campaign_report' (likely for a single report) and 'list_campaigns' (likely for campaigns, not reports), the agent has no explicit or implied direction on selection criteria, leaving usage ambiguous.

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

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