Skip to main content
Glama

list_automation_emails

Retrieve all emails in a Mailchimp automation workflow, including their status, delay, and position, to track campaign progress and optimize scheduling.

Instructions

List all emails in an automation workflow with their status, delay, and position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `list_automation_emails` tool handler function. It is decorated with @mcp.tool(), takes a workflow_id parameter, calls the Mailchimp API at /automations/{workflow_id}/emails, and returns a formatted JSON response listing all emails in an automation workflow with status, delay, and position.
    @mcp.tool()
    async def list_automation_emails(workflow_id: str) -> str:
        """List all emails in an automation workflow with their status, delay, and position."""
        mc = get_client()
        data = await mc.get(f"/automations/{workflow_id}/emails")
        emails = []
        for e in data.get("emails", []):
            s = e.get("settings", {})
            emails.append({
                "id": e.get("id", ""),
                "position": e.get("position", 0),
                "status": e.get("status", ""),
                "subject_line": s.get("subject_line", ""),
                "from_name": s.get("from_name", ""),
                "delay": e.get("delay", {}),
                "emails_sent": e.get("emails_sent", 0),
                "send_time": e.get("send_time", ""),
            })
        return _fmt({"workflow_id": workflow_id, "total_emails": len(emails), "emails": emails})
  • The tool is registered via the @mcp.tool() decorator on the `list_automation_emails` async function in the FastMCP server instance.
    @mcp.tool()
    async def list_automation_emails(workflow_id: str) -> str:
Behavior3/5

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

No annotations are present, so the description carries the burden. It mentions returned fields but omits behavioral details such as authentication requirements, rate limits, or error handling for invalid workflow IDs.

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?

A single, concise sentence that front-loads the verb and resource. No unnecessary 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?

Adequate for a simple listing tool but lacks usage guidelines and behavioral context. Given absent annotations and schema descriptions, more detail would be beneficial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description should clarify the parameter. It only implies workflow_id is the automation ID, providing minimal additional meaning beyond the parameter name.

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 lists emails in an automation workflow and specifies the returned fields (status, delay, position). This distinguishes it from siblings like list_automations which list workflows.

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?

No explicit when-to-use or alternative guidance is provided. The description implies usage for retrieving emails from a specific automation, but lacks direct differentiation from similar tools like get_automation.

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/AlexlaGuardia/mcp-mailchimp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server