Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

list_automations

Retrieve all automated email workflows from your Mailchimp account to view and manage marketing sequences.

Instructions

List all automations in your Mailchimp account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic within handleToolCall for the 'list_automations' tool. It calls the MailchimpService.listAutomations() method and returns a formatted JSON string of selected automation fields.
    case "list_automations":
      const automations = await service.listAutomations();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              automations.automations.map((a) => ({
                id: a.id,
                name: a.name,
                status: a.status,
                type: a.type,
                create_time: a.create_time,
              })),
              null,
              2
            ),
          },
        ],
      };
  • Registration of the 'list_automations' tool in getToolDefinitions array, including name, description, and empty input schema.
    {
      name: "list_automations",
      description: "List all automations in your Mailchimp account",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Type definition for MailchimpAutomation, used in the return type of listAutomations and for structuring the tool output.
    export interface MailchimpAutomation {
      id: string;
      name: string;
      status: "save" | "paused" | "sending";
      create_time: string;
      start_time?: string;
      from_name: string;
      from_email: string;
      subject: string;
      reply_to: string;
      to_name: string;
      title: string;
      type:
        | "abandonedCart"
        | "abandonedBrowse"
        | "api"
        | "bestCustomers"
        | "click"
        | "date"
        | "email"
        | "emailSeries"
        | "groupAdd"
        | "groupRemove"
        | "mandrill"
        | "product"
        | "purchase"
        | "signup"
        | "signupFollowUp"
        | "survey"
        | "visit"
        | "welcome";
      template_id?: number;
      delay?: number;
      delay_type?: "now" | "day" | "hour" | "week";
      delay_unit?: "day" | "hour" | "week";
      delay_value?: number;
      delay_direction?: "before" | "after";
      delay_full?: {
        delay_type: string;
        delay_unit: string;
        delay_value: number;
        delay_direction: string;
      };
      trigger_settings?: {
        workflow_type: string;
        workflow_title?: string;
        runtime?: {
          days?: number[];
          hours?: number[];
        };
        one_time?: boolean;
        one_time_date?: string;
      };
      tracking?: {
        opens: boolean;
        html_clicks: boolean;
        text_clicks: boolean;
        goal_tracking: boolean;
        ecomm360: boolean;
        google_analytics: string;
        clicktale: string;
        salesforce?: {
          campaign: boolean;
          notes: boolean;
        };
        capsule?: {
          notes: boolean;
        };
      };
      settings?: {
        title: string;
        from_name: string;
        reply_to: string;
        use_conversation: boolean;
        to_name: string;
        folder_id: string;
        authenticate: boolean;
        auto_footer: boolean;
        inline_css: boolean;
        auto_tweet: boolean;
        fb_comments: boolean;
        timewarp: boolean;
        template_id: number;
        drag_and_drop: boolean;
      };
      social_card?: {
        image_url?: string;
        description?: string;
        title?: string;
      };
      trigger_settings_workflow_type?: string;
      trigger_settings_workflow_title?: string;
      trigger_settings_runtime?: {
        days?: number[];
        hours?: number[];
      };
      trigger_settings_one_time?: boolean;
      trigger_settings_one_time_date?: string;
      report_summary?: {
        opens: number;
        unique_opens: number;
        open_rate: number;
        clicks: number;
        subscriber_clicks: number;
        click_rate: number;
        visits: number;
        unique_visits: number;
        conversion_rate: number;
        subscribes: number;
        ecommerce?: {
          total_revenue: number;
          currency_code: string;
          average_order_revenue: number;
          total_orders: number;
          total_products_sold: number;
        };
      };
      _links?: Array<{
        rel: string;
        href: string;
        method: string;
        targetSchema?: string;
        schema?: string;
      }>;
    }
  • Helper method in MailchimpService class that makes a paginated API request to Mailchimp's /automations endpoint to retrieve the list of automations.
    async listAutomations(): Promise<{ automations: MailchimpAutomation[] }> {
      return await this.makePaginatedRequest(
        "/automations",
        "create_time",
        "DESC"
      );
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, if it requires authentication, how results are paginated, or what format the output takes. For a list operation with zero annotation coverage, this is a significant gap.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness3/5

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

Given the tool's simplicity (no parameters, no annotations, no output schema), the description is minimally adequate but lacks completeness. It doesn't explain what 'list' means operationally (e.g., format, pagination, sorting) or how it differs from sibling tools, leaving gaps for an AI agent to infer behavior.

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 tool has zero parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline score of 4 for not adding unnecessary information.

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 verb ('List') and resource ('all automations in your Mailchimp account'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_automation_emails' or 'list_automation_subscribers', which would require more specificity about scope.

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 like 'get_automation' (for a single automation) or 'list_automation_emails' (for emails within automations). It lacks explicit when/when-not instructions or named alternatives, leaving usage context implied at best.

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