Skip to main content
Glama
damientilman

Mailchimp MCP

search_members

Search for members across all Mailchimp audiences using email or name, returning exact and fuzzy matches to find a specific person without knowing their audience.

Instructions

Search for members across all audiences by email address or name, returning both exact and fuzzy matches.

Use when looking for a specific person and you may not know which audience they belong to. Use list_audience_members instead to browse all members of a known audience. Use get_member_activity or get_member_tags after finding a member for engagement data.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). Read-only, safe to retry.

Args: query: Search query. Full email address for exact match, or name/partial email for fuzzy search. Minimum 3 characters. list_id: Optional audience/list ID to restrict search to a single audience. Obtain from list_audiences.

Returns: JSON with results array combining exact and fuzzy matches. Each result: email, status ('subscribed', 'unsubscribed', etc.), full_name, list_id (audience the member belongs to). Exact matches appear first.

Example: search_members(query="john@example.com") -> {"results": [{"email": "john@example.com", "status": "subscribed", "list_id": "abc123", ...}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
list_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Discloses authentication via API key, Mailchimp API rate limits (max 10 concurrent requests), and that it is read-only and safe to retry. Also explains return behavior (exact matches first, fuzzy matches) and response format.

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?

Well-structured with purpose first, then usage guidance, authentication/rate limits, parameter details, return format, and an example. Every sentence adds value without redundancy.

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?

Given no annotations and a search tool with moderate complexity, the description covers all necessary aspects: purpose, usage, parameters, return format, auth, rate limits, and includes an example. It is complete for effective agent usage.

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?

With 0% schema description coverage, the description fully explains both parameters: query field with details on exact vs fuzzy search and minimum 3 characters, and optional list_id with source hint. Adds significant meaning beyond the schema's type info.

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 the tool searches for members by email or name across all audiences with exact and fuzzy matches. It differentiates itself from sibling tools like list_audience_members, which is for browsing a known audience's members.

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 states when to use (looking for a specific person across audiences) and when not to use (use list_audience_members for browsing a known audience), and suggests subsequent tools (get_member_activity, get_member_tags).

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