Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_campaign_report

Retrieve detailed analytics and performance data for a specific Mailchimp email campaign to track opens, clicks, and engagement metrics.

Instructions

Get detailed report for a specific campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesThe campaign ID

Implementation Reference

  • The tool handler logic within the handleToolCall function that invokes the Mailchimp service's getCampaignReport method, processes the result, and returns a formatted text response.
    case "get_campaign_report":
      const campaignReport = await service.getCampaignReport(args.campaign_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(campaignReport, null, 2),
          },
        ],
      };
  • Input schema definition for the get_campaign_report tool, specifying an object with a required string campaign_id property.
    inputSchema: {
      type: "object",
      properties: {
        campaign_id: {
          type: "string",
          description: "The campaign ID",
        },
      },
      required: ["campaign_id"],
    },
  • Registration of the get_campaign_report tool in the getToolDefinitions array, including name, description, and input schema.
    {
      name: "get_campaign_report",
      description: "Get detailed report for a specific campaign",
      inputSchema: {
        type: "object",
        properties: {
          campaign_id: {
            type: "string",
            description: "The campaign ID",
          },
        },
        required: ["campaign_id"],
      },
    },
  • Core helper method in MailchimpService that performs the API request to retrieve the campaign report from Mailchimp's /reports/{campaignId} endpoint.
    async getCampaignReport(
      campaignId: string
    ): Promise<MailchimpCampaignReport> {
      return await this.makeRequest(`/reports/${campaignId}`);
    }
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. It implies a read-only operation ('Get') but doesn't specify permissions, rate limits, error handling, or response format. It lacks details on what 'detailed report' includes, such as metrics or structure, making it insufficient for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that front-loads the core action ('Get detailed report') and resource. It avoids unnecessary words, but could be more structured by including key details like report scope or alternatives, though it earns points for brevity.

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 tool's complexity (a report-fetching operation), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the report contains, how it's formatted, or any behavioral traits like data freshness or access requirements, leaving significant gaps for the agent.

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 the 'campaign_id' parameter fully documented in the schema. The description doesn't add any meaning beyond the schema, such as format examples or contextual usage of the ID. Baseline score of 3 is appropriate since the schema does the heavy lifting.

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 states the tool's purpose with a clear verb ('Get') and resource ('detailed report for a specific campaign'), but it's vague about what constitutes a 'detailed report' and doesn't distinguish it from sibling tools like 'get_campaign' or 'list_campaign_reports'. It provides basic functionality but lacks specificity in scope or content.

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 offers no guidance on when to use this tool versus alternatives, such as 'get_campaign' for basic campaign info or 'list_campaign_reports' for multiple reports. It doesn't mention prerequisites, exclusions, or contextual cues, leaving the agent to infer usage 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/AgentX-ai/mailchimp-mcp'

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