Skip to main content
Glama

mailchimp_list_campaigns

List Mailchimp email campaigns with optional filters for status and audience. Integrate campaign data into automation and analysis workflows.

Instructions

List Mailchimp email campaigns, optionally filtered by status or audience.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesMailchimp API key
countNoNumber of campaigns (default: 10)
statusNoFilter by campaign status
list_idNoFilter by audience ID
Behavior2/5

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

No annotations provided, and the description does not disclose read-only nature, pagination behavior, rate limits, or return format. The agent is left uninformed about expected behavior beyond listing.

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?

The single sentence is concise and front-loads the core purpose. However, it lacks structure (e.g., bullet points) and could be slightly more informative without losing brevity.

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

Completeness2/5

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

With no output schema and no annotations, the description is incomplete. It does not explain what the tool returns, pagination, or any prerequisites beyond the API key.

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 coverage is 100%, so the baseline is 3. The description adds reinforcement by mentioning 'filtered by status or audience' but no additional meaning beyond the 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?

The description clearly states the action (List) and resource (Mailchimp email campaigns), and specifies optional filtering by status or audience, distinguishing it from sibling tools like mailchimp_get_campaign.

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 on when to use this tool vs alternatives (e.g., mailchimp_get_campaign or mailchimp_search_members), nor any contextual conditions for its use.

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/malamutemayhem/unclick'

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