Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_audiences_batch_subscribe

Batch subscribe or update up to 500 audience members in a single API call, with support for tags, interests, merge fields, and language.

Instructions

Batch subscribe or update multiple members in a single API call (up to 500 members)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>",
      "members": "<members>"
    },
    "name": "mailchimp_audiences_batch_subscribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYesList/audience ID
membersYesArray of member objects to subscribe/update
update_existingNoWhether to update existing subscribers (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only mentions the action and the 500-member limit, but does not reveal side effects (e.g., partial success handling), whether existing members are updated by default, or what the response contains. This is a significant transparency gap for a mutation tool.

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

Conciseness5/5

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

The description is a single, well-structured sentence that front-loads the core purpose and includes a key constraint (500 members). Every word earns its place; there is no fluff or redundancy.

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 the full parameter schema and the absence of an output schema, the description provides the minimum viable information: what the tool does and its main limit. However, it omits important contextual details such as error handling, partial success behavior, or prerequisites, which would be valuable for a batch mutation operation.

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

Parameters4/5

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

The schema covers all parameters with descriptions, so baseline is 3. The description adds meaningful context by stating the batch limit (up to 500) and clarifying that each member can be subscribed or updated, which enriches the interpretation of the 'members' array without contradicting the schema.

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?

Description specifies a clear action (batch subscribe or update) on a resource (members) with a scope (up to 500 members), making the tool's purpose immediately understandable. However, it does not explicitly differentiate from the closely named sibling 'mailchimp_lists_batch_subscribe', which serves the same core purpose, so it lacks clear sibling distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for batch operations on up to 500 members but provides no explicit guidance on when to prefer this tool over alternatives like single-member add/update or the analogous 'lists_batch_subscribe'. No exclusions or alternative recommendations are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools