Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_automation_email_report

Retrieve performance data for automated email campaigns in Mailchimp to analyze opens, clicks, and engagement metrics.

Instructions

Get automation email report data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesThe workflow ID of the automation
email_idYesThe email ID within the automation

Implementation Reference

  • Core handler function that executes the tool logic by making an API request to Mailchimp to retrieve the automation email report.
    async getAutomationEmailReport(
      workflowId: string,
      emailId: string
    ): Promise<any> {
      return await this.makeRequest(
        `/automations/${workflowId}/emails/${emailId}`
      );
    }
  • Tool definition including name, description, and input schema for validation.
    {
      name: "get_automation_email_report",
      description: "Get automation email report data",
      inputSchema: {
        type: "object",
        properties: {
          workflow_id: {
            type: "string",
            description: "The workflow ID of the automation",
          },
          email_id: {
            type: "string",
            description: "The email ID within the automation",
          },
        },
        required: ["workflow_id", "email_id"],
      },
    },
  • Registration and dispatch handler in the tool call switch statement that invokes the service method and formats the response.
    case "get_automation_email_report":
      const emailReport = await service.getAutomationEmailReport(
        args.workflow_id,
        args.email_id
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(emailReport, null, 2),
          },
        ],
      };
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. It states 'Get' implies a read operation, but it doesn't disclose behavioral traits such as authentication requirements, rate limits, error conditions, or what format the report data is returned in. The description is minimal and lacks necessary 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 with zero waste. It's front-loaded and appropriately sized for a simple retrieval tool, making it easy to parse quickly without unnecessary elaboration.

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 read operation with 2 required parameters) and lack of annotations and output schema, the description is incomplete. It doesn't explain what the report data includes, how it's structured, or any behavioral aspects. For a tool that likely returns detailed data, more context is needed to be fully useful.

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 'workflow_id' and 'email_id'. The description adds no additional meaning beyond the schema, as it doesn't explain parameter relationships or usage nuances. With high schema coverage, the baseline score of 3 is appropriate, as the schema adequately handles parameter semantics.

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 'Get automation email report data' states a clear verb ('Get') and resource ('automation email report data'), but it's vague about what specific data is retrieved. It distinguishes from siblings like 'get_automation_email' (likely gets email content) and 'get_automation_report' (likely gets general automation report), but the distinction is not explicitly articulated in the description itself.

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_automation_email' and 'get_automation_report', there's no indication of context, prerequisites, or exclusions. Usage is implied only by the tool name, not described.

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