Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_automation_report

Retrieve automation workflow performance data from Mailchimp to analyze email campaign effectiveness and subscriber engagement metrics.

Instructions

Get automation report data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesThe workflow ID of the automation

Implementation Reference

  • Core handler function that executes the tool logic by fetching automation emails report from Mailchimp API endpoint `/automations/${workflowId}/emails`.
    async getAutomationReport(workflowId: string): Promise<any> {
      return await this.makeRequest(`/automations/${workflowId}/emails`);
    }
  • Input schema definition for the get_automation_report tool, requiring a workflow_id string.
    inputSchema: {
      type: "object",
      properties: {
        workflow_id: {
          type: "string",
          description: "The workflow ID of the automation",
        },
      },
      required: ["workflow_id"],
    },
  • Tool registration in getToolDefinitions array, defining name, description, and input schema.
    {
      name: "get_automation_report",
      description: "Get automation report data",
      inputSchema: {
        type: "object",
        properties: {
          workflow_id: {
            type: "string",
            description: "The workflow ID of the automation",
          },
        },
        required: ["workflow_id"],
      },
    },
  • MCP tool handler in handleToolCall switch that invokes the service method and returns formatted JSON response.
    case "get_automation_report":
      const report = await service.getAutomationReport(args.workflow_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(report, null, 2),
          },
        ],
      };
Behavior1/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. 'Get automation report data' implies a read-only operation, but it doesn't specify if authentication is needed, rate limits apply, what format the data is in, or if it's paginated. This is inadequate 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly, though its brevity contributes to gaps in other dimensions.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what the report data includes, how it's structured, or any behavioral traits. For a tool that likely returns complex report data, this leaves significant gaps for an AI agent to understand its 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?

The input schema has 100% description coverage, with 'workflow_id' clearly documented. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without compensating value.

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

Purpose2/5

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

The description 'Get automation report data' states a verb ('Get') and resource ('automation report data'), but it's vague about what specific data is retrieved and doesn't distinguish from siblings like 'get_automation_email_report' or 'list_automation_subscribers'. It's better than a tautology but lacks specificity about the report's 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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_automation' (likely for automation details) and 'get_automation_email_report' (likely for email-specific reports), the description offers no context on differentiation, leaving the agent to guess based on tool names 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