Skip to main content
Glama

create_campaign

Create email campaigns in Mailchimp by specifying recipients, subject line, sender details, and campaign type to send marketing communications.

Instructions

Create a new email campaign. Returns the campaign ID. Type: regular, plaintext, absplit, rss.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
subject_lineYes
from_nameYes
reply_toYes
titleNo
preview_textNo
campaign_typeNoregular

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the create_campaign tool, which handles the request to create a new email campaign in Mailchimp.
    async def create_campaign(
        list_id: str,
        subject_line: str,
        from_name: str,
        reply_to: str,
        title: str = "",
        preview_text: str = "",
        campaign_type: str = "regular",
    ) -> str:
        """Create a new email campaign. Returns the campaign ID. Type: regular, plaintext, absplit, rss."""
        mc = get_client()
        body: dict[str, Any] = {
            "type": campaign_type,
            "recipients": {"list_id": list_id},
            "settings": {
                "subject_line": subject_line,
                "from_name": from_name,
                "reply_to": reply_to,
                "title": title or subject_line,
            },
        }
        if preview_text:
            body["settings"]["preview_text"] = preview_text
        c = await mc.post("/campaigns", json=body)
        return _fmt({
            "id": c["id"],
            "status": c.get("status", ""),
            "title": c.get("settings", {}).get("title", ""),
            "message": "Campaign created successfully.",
        })
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the return value ('Returns the campaign ID') and campaign types, but lacks critical information about permissions needed, rate limits, whether this is an asynchronous operation, error conditions, or what happens with invalid inputs.

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 description is appropriately brief with two sentences that convey the core functionality and return value. The campaign type enumeration is efficient, though it could be more structured. No wasted words or redundant information.

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?

For a creation tool with 7 parameters, 0% schema coverage, and no annotations, the description is insufficient. While an output schema exists, the description lacks crucial context about permissions, constraints, campaign type differences, and how parameters interact. It doesn't compensate for the missing structured documentation.

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

Parameters2/5

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

With 0% schema description coverage for 7 parameters, the description provides minimal parameter information. It mentions campaign types but doesn't explain what each type means or how they differ. No other parameters are described, leaving most of the input schema undocumented.

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 clearly states the action ('Create a new email campaign') and resource ('email campaign'), making the purpose immediately understandable. It distinguishes from siblings like 'replicate_campaign' or 'update_campaign' by specifying creation of a new campaign, though it doesn't explicitly contrast with all alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives like 'replicate_campaign' or 'update_campaign'. It mentions campaign types but doesn't explain when each type is appropriate or what prerequisites exist for creating campaigns.

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

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