Skip to main content
Glama
damientilman

Mailchimp MCP

list_campaign_folders

List Mailchimp campaign folders and their campaign counts. Use to view folder structure for organizing campaigns without affecting delivery.

Instructions

List campaign folders used to organize campaigns in the Mailchimp dashboard.

Folders are organizational containers only; they do not affect campaign delivery or behavior. Returns an empty array if no folders exist. Do not use to find campaigns; use list_campaigns or search_campaigns instead.

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

Args: count: Number of folders to return (1-1000, default 50). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and folders array. Each folder: id, name, count (campaigns in folder).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses authentication method, max concurrent requests, read-only safety, and that folders do not affect delivery behavior.

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?

Well-structured with clear sections for description, usage guidelines, and parameters. Front-loaded with purpose, every sentence adds value.

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

Completeness5/5

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

Output schema exists, and description specifies return format (JSON with total_items and folders array with id, name, count), making it complete.

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?

Input schema has 0% coverage, but description explains count range (1-1000, default 50) and offset pagination purpose, adding meaning 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 'List campaign folders' and explains they organize campaigns, differentiating from list_campaigns and search_campaigns by advising not to use it for finding campaigns.

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 says 'Do not use to find campaigns; use list_campaigns or search_campaigns instead,' providing clear when-not-to-use and alternatives. Also notes returns empty array if no folders.

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