Skip to main content
Glama
damientilman

Mailchimp MCP

search_automation_campaigns

Read-only

List campaigns sent by Mailchimp automations and Customer Journeys. Use this to see which emails your automations recently sent, filtering by status, date, or audience.

Instructions

List campaigns originated by an automation or a Customer Journey (campaign type='automation').

Every email Mailchimp sends from a Classic automation or a Customer Journey creates a campaign object with type='automation'. This tool filters /campaigns to surface only those, so you can answer "what did my automations send recently?" without scanning all campaigns.

Use this as the most practical workaround for the lack of a public Customer Journeys read API: while you can't list the journeys themselves, you can list the campaigns they emit. Use list_automations for Classic-only metadata (journey internals aren't exposed). Use list_campaigns for the full campaign feed.

Args: count: Number of campaigns to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count. list_id: Optional audience ID to restrict to a single audience. Obtain from list_audiences. status: Filter by campaign status. Valid values: 'save', 'paused', 'schedule', 'sending', 'sent'. Omit for all. since_send_time: Only return campaigns sent after this ISO 8601 datetime (e.g. '2026-04-01T00:00:00Z'). before_send_time: Only return campaigns sent before this ISO 8601 datetime.

Returns: JSON with total_items and campaigns array. Each campaign: id, status, title, subject_line, send_time, emails_sent, list_id, list_name. Useful to compute automation send volume and identify which automation/journey produced which email (via title patterns).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo
statusNo
accountNo
list_idNo
since_send_timeNo
before_send_timeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond annotations (readOnlyHint=true), the description adds valuable context: it explains that the tool filters /campaigns, describes the return structure (JSON with total_items and campaigns array), and states the limitation regarding Customer Journeys. This fully discloses behavior and purpose.

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 well-structured: it opens with the core purpose, then provides context, usage guidance, parameter details, and return information. Every sentence serves a distinct purpose without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 7 parameters, annotations, and an output schema, the description covers purpose, usage, and most parameters thoroughly. However, the missing 'account' parameter documentation reduces completeness slightly. Overall, it is highly informative.

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

Parameters4/5

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

The description documents most parameters (count, offset, list_id, status, since_send_time, before_send_time) with their meanings and defaults, adding significant value beyond the schema. However, it omits the 'account' parameter present in the schema, leaving a gap in coverage.

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 explicitly states 'List campaigns originated by an automation or a Customer Journey (campaign type='automation')', providing a clear verb+resource. It distinguishes from siblings by referencing list_automations and list_campaigns, ensuring the agent understands its specific niche.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool: 'most practical workaround for the lack of a public Customer Journeys read API.' It also specifies alternatives: 'Use list_automations for Classic-only metadata' and 'Use list_campaigns for the full campaign feed.' This clearly helps in tool selection.

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

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