Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by AlexlaGuardia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

batch_subscribe_members

Batch subscribe up to 500 members to a Mailchimp list by providing a list ID and comma-separated emails. Add subscribers in bulk to grow your audience.

Instructions

Batch subscribe multiple members at once. emails: comma-separated list (max 500).

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>",
      "emails": "<emails>"
    },
    "name": "batch_subscribe_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
list_idYes
emailsYes
statusNosubscribed

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states batch subscription but omits behavioral details like idempotency, duplicate handling, or required permissions, leaving gaps.

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?

Two short sentences, front-loaded with purpose and key constraint. No redundant words; each sentence adds essential 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?

Despite an output schema existing, the description lacks context on the 'status' parameter, does not mention required fields beyond 'emails', and omits side effects or processing behavior, making it incomplete for a 3-parameter tool.

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?

Schema description coverage is 0%, so description must compensate. It only clarifies the 'emails' parameter (comma-separated, max 500) but fails to describe 'list_id' or 'status', which have default values and no explanation.

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?

Description explicitly states 'Batch subscribe multiple members at once,' clearly identifying the verb (subscribe) and resource (members). Differentiates from siblings like add_or_update_member (single) and archive_member.

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?

Indicates usage via 'comma-separated list (max 500),' but does not provide explicit when-to-use or when-not-to-use guidance, nor compare to alternative tools like add_or_update_member.

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