Skip to main content
Glama
Sign In
mailchimp-mcp

mailchimp-mcp

by livemau5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

search_members

Locate audience members by name or email address across all audiences. Narrow results to a specific list using list ID.

Instructions

Search for audience members by name or email address across all audiences.

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": {
      "query": "<query>"
    },
    "name": "search_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query (name or email address)
list_idNoLimit search to a specific audience/list ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses the search scope and criteria but omits behavioral details such as return format, pagination, permission requirements, or whether partial matches are returned.

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, concise sentence with no wasted words. It front-loads the action ('Search for audience members') and lists criteria and scope efficiently.

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?

The tool has no output schema, so the description should explain what is returned. It only says 'search for' without stating the output format or any limitations. Given the tool's simplicity, it's adequate but incomplete for a fully opaque context.

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 covers both parameters with descriptions (query is name/email, list_id limits to a specific audience). The tool description adds that search is across all audiences, implying the list_id is a limiter, but this is minor extra value 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 uses the specific verb 'Search' with resource 'audience members' and scope 'across all audiences', clearly distinguishing from generic sibling 'search'. It states exactly what the tool does and its default search scope.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool (finding members by name/email across all audiences) but does not explicitly mention alternatives or exclusions relative to siblings like 'search' or 'list_audiences'.

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