Mailchimp MCP Server

mailchimp_automations_list_queue

Retrieve all subscribers in the automation email queue. Provide workflow ID and email ID to get the list.

Instructions

Get all subscribers in the queue for an automation email

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workflow_id": "<workflow_id>",
      "email_id": "<email_id>"
    },
    "name": "mailchimp_automations_list_queue"
  }
}

Input Schema

Name	Required	Description	Default
`email_id`	Yes	Automation email ID
`workflow_id`	Yes	Automation workflow ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for disclosing behavior. It does not mention response format, pagination, or error conditions, and the word 'all' may inaccurately imply a single complete list rather than a paginated result. This leaves the agent with incomplete behavioral expectations.

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, tightly-worded sentence that front-loads the action and object. It contains no fluff, redundancy, or extraneous detail, making it highly concise and well-structured.

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?

For a tool with two simple parameters and no output schema, the description gives the core purpose but omits any indication of the response structure or usage constraints. It is minimally sufficient but leaves ambiguity about what a caller should expect, especially regarding result size or formatting.

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 already provides clear descriptions for both required parameters (workflow_id and email_id), achieving 100% coverage. The description adds no extra semantic detail beyond what the schema provides, so the baseline of 3 is appropriate.

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

Purpose5/5

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

The description uses a specific verb ('Get') and resource ('all subscribers in the queue for an automation email'), clearly distinguishing it from sibling tools like mailchimp_automations_add_to_queue or mailchimp_automations_list. The purpose is unambiguous and immediately understood.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies its use for reading the queue of an automation email, but it provides no explicit guidance on when to choose it over alternatives. Since no sibling tool directly lists queue subscribers, the usage context is inferred rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server