Skip to main content
Glama
damientilman

Mailchimp MCP

list_merge_fields

Retrieve merge fields defined for a Mailchimp audience to discover available tags and field details before adding or updating members.

Instructions

List merge fields (custom data fields) defined for an audience, including tags, types, and defaults.

Use to discover available merge fields and their tag names before adding or updating members. Default fields (FNAME, LNAME, ADDRESS, PHONE) are always present. Use create_merge_field to add custom fields. Merge field tags are used in add_member/update_member merge_fields objects and in email content as |TAG| merge tags.

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

Args: list_id: The Mailchimp audience/list ID (e.g. 'abc123def4'). Obtain from list_audiences. count: Number of merge fields to return (1-1000, default 50). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and merge_fields array. Each field: merge_id (int, use with update_merge_field/delete_merge_field), tag (string, e.g. 'FNAME'), name (display name), type ('text', 'number', 'date', etc.), required (boolean), default_value, options (choices for dropdown/radio types).

Example: list_merge_fields(list_id="abc123") -> {"total_items": 6, "merge_fields": [{"merge_id": 1, "tag": "FNAME", "name": "First Name", "type": "text", ...}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden. It discloses authentication via API key, rate limits (max 10 concurrent requests), and declares the operation as read-only and safe to retry. This fully informs the agent about behavioral characteristics.

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 well-structured: purpose, usage context, behavioral info, parameter details, return format, and example. Each sentence adds necessary information, no fluff. Front-loaded with key action and resource.

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?

The description covers all relevant aspects: tool purpose, when to use, behavioral traits, parameter details, output structure (including example with field types), and relationships to sibling tools. It is complete for a tool with 3 parameters and no nested objects, and even includes an example 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?

Schema description coverage is 0%, so the description must compensate. It provides detailed meanings for all three parameters: list_id (with example and how to obtain), count (range and default), and offset (pagination usage). This adds significant 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 clearly states that the tool lists merge fields for an audience, including tags, types, and defaults. It distinguishes itself from sibling tools like create_merge_field, update_merge_field, and delete_merge_field by focusing on listing existing fields.

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 advises using this tool to discover merge fields before adding or updating members. Mentions default fields are always present and references create_merge_field for custom fields. Also explains how tags are used in other operations like add_member/update_member and email content, providing clear context for when to use this tool.

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