Skip to main content
Glama
damientilman

Mailchimp MCP

create_interest

Add a new selectable interest option to an existing interest category, making it available on signup forms.

Instructions

Create a new interest option within an interest category (e.g. add "Tech" to a "Topics" category).

Use after create_interest_category to add selectable options. Each option becomes available on signup forms (unless category type is 'hidden'). Use list_interests to check existing options. Use delete_interest to remove an option.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). Respects read-only and dry-run modes.

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. category_id: The interest category ID. Obtain from list_interest_categories or create_interest_category. name: Display name for the interest option (e.g. 'Tech', 'Sports'). Must be unique within the category.

Returns: JSON with fields: id (string, use with delete_interest), name, subscriber_count (int, starts at 0).

Example: create_interest(list_id="abc123", category_id="cat456", name="Technology") -> {"id": "int789", "name": "Technology", "subscriber_count": 0}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
category_idYes
nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses authentication, rate limits, read-only/dry-run modes, and side effects (availability on signup forms). Could mention error handling or concurrency, but still very transparent.

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?

Well-structured with sections and a useful example. Every sentence adds value. Slightly verbose on authentication, but overall concise given the detail needed.

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?

Covers parameters, return values (with output schema), prerequisites, authentication, rate limits, side effects, and example. Complete for a creation tool with 3 parameters and no annotations.

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?

Schema description coverage is 0%, but the description explains each parameter: list_id (source, example), category_id (source), name (display name, uniqueness constraint). This adds significant 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 it creates a new interest option within an interest category, using specific verbs and resource nouns. It distinguishes from sibling tools like create_interest_category, list_interests, and delete_interest by explaining the workflow.

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 to use after create_interest_category and before list_interests/delete_interest. Provides context for when the option becomes available and mentions alternatives for checking existing options or removing them.

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