Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

list_automation_emails

Retrieve all emails from a Mailchimp automation workflow to monitor content and track campaign sequences.

Instructions

List all emails in an automation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYesThe workflow ID of the automation

Implementation Reference

  • Tool handler that calls the service method and formats the response.
    case "list_automation_emails":
      const emails = await service.listAutomationEmails(args.workflow_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              emails.emails.map((e) => ({
                id: e.id,
                position: e.position,
                status: e.status,
                subject_line: e.settings.subject_line,
                emails_sent: e.emails_sent,
              })),
              null,
              2
            ),
          },
        ],
      };
  • Tool registration including name, description, and input schema.
    {
      name: "list_automation_emails",
      description: "List all emails in an automation",
      inputSchema: {
        type: "object",
        properties: {
          workflow_id: {
            type: "string",
            description: "The workflow ID of the automation",
          },
        },
        required: ["workflow_id"],
      },
    },
  • Core service method implementing the API call to list automation emails.
    async listAutomationEmails(
      workflowId: string
    ): Promise<{ emails: MailchimpAutomationEmail[] }> {
      return await this.makePaginatedRequest(
        `/automations/${workflowId}/emails`,
        "send_time",
        "DESC"
      );
    }
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 of behavioral disclosure. It states the action ('List all emails') but lacks details on permissions, rate limits, pagination, return format, or error handling. This is a significant gap for a tool with no structured safety hints.

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 without unnecessary words. It is front-loaded and appropriately sized for a simple listing tool, with no wasted information.

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 lack of annotations and output schema, the description is incomplete. It does not address behavioral aspects like what 'all emails' entails (e.g., pagination, filtering), potential errors, or the response structure. For a tool with no structured safety or output information, more context is needed to guide effective 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 description does not mention parameters, but the input schema has 100% coverage with a clear description for 'workflow_id'. Since the schema fully documents the single required parameter, the baseline score of 3 is appropriate, as the description adds no extra semantic value beyond what the schema provides.

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 ('emails in an automation'), making the purpose specific and understandable. However, it does not explicitly differentiate from sibling tools like 'get_automation_email' or 'list_automation_subscribers', which could cause confusion about scope or filtering options.

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. It does not mention prerequisites (e.g., needing a workflow ID), exclusions, or comparisons to siblings such as 'get_automation_email' (which might fetch a single email) or 'list_automation_subscribers' (which focuses on subscribers).

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