Skip to main content
Glama
damientilman

Mailchimp MCP

list_merge_fields

Read-only

Retrieve merge fields defined for a Mailchimp audience, including tags, types, and defaults. Use to discover available fields 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.

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
countNo
offsetNo
accountNo
list_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations declare readOnlyHint=true, no contradiction. Description adds context: operation is read-only, lists defaults always present, explains pagination behavior. No hidden destructive actions disclosed, but sufficient given annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured with sections, Args list, Returns, Example. Somewhat lengthy but every sentence adds value. Could be slightly more concise but still efficient.

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 4 parameters, output schema exists, description is comprehensive: covers purpose, usage, all params (except account), return format, example. No missing context for effective tool selection and use.

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 0%, so description compensates: explains list_id source, count range/default, offset pagination. However, misses the 'account' parameter entirely, leaving a gap. Other parameters well described.

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 clearly states it lists merge fields for an audience (specific verb+resource). It distinguishes from sibling tools like create_merge_field by explaining its role in discovery before member updates.

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: to discover merge fields before adding/updating members. Mentions default fields always present and directs to create_merge_field for custom fields. Also explains usage of merge tags in content and other tools.

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