Skip to main content
Glama

create_audience

Create a new Mailchimp audience/list for email marketing campaigns by specifying audience name, sender email, and company details.

Instructions

Create a new audience/list. Requires name, sender email, and company name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
from_emailYes
companyYes
permission_reminderNoYou signed up on our website.
from_nameNo
countryNoUS

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The implementation of the 'create_audience' tool, which takes audience details and posts to the Mailchimp '/lists' endpoint. The registration is implied by the @mcp.tool() decorator, although the decorator appears to be just above the function definition (line 417).
    async def create_audience(
        name: str,
        from_email: str,
        company: str,
        permission_reminder: str = "You signed up on our website.",
        from_name: str = "",
        country: str = "US",
    ) -> str:
        """Create a new audience/list. Requires name, sender email, and company name."""
        mc = get_client()
        body = {
            "name": name,
            "permission_reminder": permission_reminder,
            "email_type_option": True,
            "contact": {
                "company": company,
                "address1": "",
                "city": "",
                "state": "",
                "zip": "",
                "country": country,
            },
            "campaign_defaults": {
                "from_name": from_name or company,
                "from_email": from_email,
                "subject": "",
                "language": "en",
            },
        }
        a = await mc.post("/lists", json=body)
        return _fmt({
            "id": a["id"],
            "name": a.get("name", ""),
            "message": "Audience created.",
        })
Behavior2/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral information. It states this is a creation operation (implies mutation) and mentions required parameters, but doesn't disclose permissions needed, rate limits, whether the operation is idempotent, what happens on duplicate names, or what the output contains. For a mutation tool with zero annotation coverage, this is inadequate.

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 concise with a single sentence that states the purpose and key requirements. It's front-loaded with the main action. However, it could be slightly more structured by separating purpose from requirements.

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

Completeness3/5

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

Given this is a mutation tool with 6 parameters (3 required), 0% schema description coverage, no annotations, but with an output schema, the description is minimally adequate. The output schema reduces the need to describe return values, but the description should provide more context about the creation operation, parameter meanings, and usage scenarios to be truly complete.

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 0%, so the description must compensate but only partially does. It mentions three required parameters (name, sender email, company name) but doesn't explain what 'sender email' represents, what format 'company' expects, or mention the three optional parameters (permission_reminder, from_name, country). The description adds some meaning but leaves most parameters 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 audience/list') and specifies the required resources (name, sender email, company name). It distinguishes from siblings like 'list_audiences' (read) or 'get_audience' (retrieve), but doesn't explicitly differentiate from other creation tools like 'create_campaign' or 'create_segment'.

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 mentions required parameters but provides no guidance on when to use this tool versus alternatives. It doesn't explain what an 'audience/list' is used for, when to create one versus using existing audiences, or how it relates to sibling tools like 'create_campaign' or 'create_segment'.

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