Skip to main content
Glama
damientilman

Mailchimp MCP

search_automation_campaigns

List emails sent by Mailchimp automations or Customer Journeys. Use this to identify campaign output from automations without scanning all campaigns.

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.

Authenticated via API key. Max 10 concurrent requests. Read-only, safe to retry.

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
list_idNo
statusNo
since_send_timeNo
before_send_timeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided. Description reveals read-only nature, safety for retry, authentication method, and concurrency limit. Could mention if any side effects exist but clearly read-only.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections and no redundant information. Slightly longer than necessary but earns its place.

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 no annotations, 6 parameters, and output schema exists, description adequately covers return format and fields. Completeness is good for the complexity.

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

Parameters5/5

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

Schema coverage is 0%, but description explains all six parameters in detail: count range, offset purpose, list_id source, status valid values, datetime formats. Adds significant value beyond schema.

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?

Description clearly states it lists automation campaigns (type='automation') and differentiates from siblings like list_campaigns and list_automations. Specific verb 'list' with resource 'campaigns originated by automation/Customer Journey'.

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?

Explicitly tells when to use (to answer what automations sent recently), when not to (use list_campaigns for full feed, list_automations for Classic-only), and provides alternative tools, fulfilling all guidelines.

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