Skip to main content
Glama

mailchimp_create_campaign

Create a Mailchimp email campaign using an audience list and subject line, with optional sender name and reply-to address.

Instructions

Create a new Mailchimp email campaign.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesMailchimp API key
list_idYesAudience (list) ID to send to
subject_lineYesEmail subject line
typeNoCampaign type (default: regular)
from_nameNoSender display name
reply_toNoReply-to email address
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only says 'create' without disclosing behavioral traits such as success/error handling, permissions needed, or side effects (e.g., does it create a draft or send immediately?). Minimal transparency.

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

Conciseness3/5

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

The description is a single sentence, which is concise but lacks substance. It is not bloated, but it also fails to add value. Score 3: adequate but borderline under-specified.

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?

Given the tool's complexity (6 parameters, no output schema, no annotations), the description is insufficient. It does not explain the return value, campaign type implications, or validation behavior. A more complete description would aid agent decision-making.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema properties. It does not explain defaults, relationships between parameters, or formatting requirements. Score 3 as schema already covers parameters.

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

Purpose4/5

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

The description 'Create a new Mailchimp email campaign' clearly states the verb and resource. The name and sibling tools (e.g., mailchimp_add_member, mailchimp_get_campaign) provide implicit differentiation, though the description itself does not explicitly distinguish from siblings. Score 4 for clear but not fully differentiated.

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 provided on when to use this tool versus alternatives (e.g., when to create a campaign vs. add a member). No prerequisites, context, or exclusions are mentioned. Score 2 for no usage guidance.

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