Skip to main content
Glama

start_automation

Start all emails in a Mailchimp classic automation workflow to activate scheduled email sequences for marketing campaigns.

Instructions

Start all emails in a classic automation workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the 'start_automation' tool handler in mcp_mailchimp/server.py. It uses the Mailchimp client to trigger the start-all-emails action on a specified workflow.
    @mcp.tool()
    async def start_automation(workflow_id: str) -> str:
        """Start all emails in a classic automation workflow."""
        mc = get_client()
        await mc.post(f"/automations/{workflow_id}/actions/start-all-emails")
        return _fmt({"workflow_id": workflow_id, "message": "Automation started."})
Behavior2/5

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

No annotations are provided, so the description carries full burden. It implies a mutation action ('Start'), suggesting potential side effects like triggering emails, but doesn't disclose behavioral traits such as permissions needed, whether it's idempotent, rate limits, or what happens if the workflow is already running. This leaves critical gaps for safe usage.

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, clear sentence with zero wasted words. It's front-loaded with the core action and target, making it easy to parse quickly. Every word contributes directly to the tool's purpose.

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 one parameter with 0% schema coverage and no annotations, the description is minimal but not complete. It lacks details on behavior, output (though an output schema exists, reducing burden), and usage context. For a mutation tool with no annotations, it should provide more guidance on effects and prerequisites to be fully helpful.

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 description coverage is 0%, so the description must compensate. It mentions 'workflow' contextually but adds no meaning beyond the schema's 'workflow_id' parameter—no details on format, sourcing, or validation. With one parameter and no schema descriptions, the baseline is 3 as it minimally implies the parameter's role without enhancing understanding.

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

Purpose3/5

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

The description states the action ('Start all emails') and target ('in a classic automation workflow'), which gives a basic understanding of purpose. However, it's vague about what 'start all emails' means operationally and doesn't distinguish this tool from sibling tools like 'pause_automation' or 'list_automations' beyond the verb difference.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether the automation must be paused or draft), exclusions, or relationships to sibling tools like 'pause_automation' or 'list_automations'. The description lacks context for decision-making.

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