Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_merge_fields_list

Retrieve all merge fields (custom fields) for a Mailchimp audience list. Filter by type, required status, and use count/offset to paginate results.

Instructions

Get all merge fields (custom fields) for a list/audience

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

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by merge field type
countNoNumber of records to return (default 10)
offsetNoNumber of records to skip
list_idYesList/audience ID
requiredNoFilter by required status

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full transparency burden, but it only says 'Get all merge fields' and does not disclose pagination behavior, default count, or return format. The presence of 'count' and 'offset' in the schema suggests pagination, but the description doesn't clarify that 'all' is subject to these limits.

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, front-loaded sentence with no extraneous wording. It efficiently conveys the core purpose and parenthetical clarification.

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 five parameters and no output schema, so the description should compensate for missing return/behavior details. It doesn't mention response structure, pagination, or filtering capabilities, though the schema covers parameters. Overall, it's minimally adequate for a list operation but lacks richness.

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 coverage is 100% with descriptions for all five parameters, so the baseline is 3. The description adds contextual meaning by equating merge fields to custom fields and indicating the scope (list/audience), but it does not elaborate on parameter usage beyond what the schema already provides.

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 verb ('Get') and the resource ('all merge fields'), explicitly clarifying that merge fields are custom fields and scoping to 'a list/audience'. This distinguishes it from sibling tools like merge_fields_get, which likely fetches a single merge field.

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 retrieving all merge fields for a list/audience, but it provides no explicit when-to-use guidance or differentiation from alternatives such as merge_fields_get or create. There is no mention of prerequisites or excluded scenarios.

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