Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_automation_queue_subscriber

Read-only

Retrieve the queue status of a specific subscriber within a classic automation email by providing the workflow ID, email ID, and subscriber's email address.

Instructions

Get a single subscriber from the queue of a classic automation email.

Retrieves the queue status for a specific subscriber within an automation email. The subscriber is located by hashing the provided email address.

Args: workflow_id: The unique id of the classic automation workflow. workflow_email_id: The unique id of the automation email whose queue to inspect. email_address: The email address of the queued subscriber to look up.

Returns: JSON with the queued subscriber details.

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>",
      "workflow_email_id": "<workflow_email_id>",
      "email_address": "<email_address>"
    },
    "name": "get_automation_queue_subscriber"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
workflow_idYes
email_addressYes
workflow_email_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context: the subscriber is located by hashing the email, and it retrieves queue status. This adds value beyond annotations but does not disclose other behaviors like auth needs or rate limits.

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 concise and front-loaded with the purpose. It uses a clear structure with a short paragraph followed by an args list. Every sentence adds value with no wasted words.

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 has an output schema, the description mentions returns. However, it lacks details on potential errors, prerequisites, or the hashing mechanism. The optional 'account' parameter is not addressed, and there is no guidance on when to use this vs list.

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?

Schema coverage is 0%, so the description carries the burden. It explains the three required parameters (workflow_id, workflow_email_id, email_address) with clear roles but omits the optional 'account' parameter. Thus, it adds meaning to most but not all parameters.

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 clearly states the tool gets a single subscriber from the queue of a classic automation email. It uses a specific verb ('get') and resource ('subscriber'), and distinguishes itself from siblings like 'add_automation_queue_subscriber' (adds), 'get_automation_email_queue' (lists all), and 'get_automation_removed_subscriber' (gets removed).

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 the context (inspecting a specific subscriber's queue status) but does not explicitly state when to use this tool vs alternatives like 'get_automation_email_queue'. No direct when-to-use or when-not-to-use guidance is provided.

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

Deploy Server

Other Tools