Skip to main content
Glama
damientilman

Mailchimp MCP

get_segment

Retrieve full details of a specific Mailchimp segment, including member count and filter conditions. Inspect a segment's type or verify conditions.

Instructions

Retrieve full details of a specific segment including member count and filter conditions.

Use to inspect a segment's conditions or verify its type and member count. Use list_segments to browse all segments. Use list_segment_members to see individual members in the segment.

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. segment_id: The segment ID (numeric string, e.g. '12345'). Obtain from list_segments.

Returns: JSON with fields: id, name, member_count (int), type ('static' for tags, 'saved' for dynamic segments), created_at (ISO 8601), updated_at (ISO 8601), options (object with match and conditions for dynamic segments, null for static segments).

Example: get_segment(list_id="abc123", segment_id="12345") -> {"id": 12345, "name": "VIP", "member_count": 150, "type": "static", ...}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
segment_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided; description adds key behavioral context: authentication via API key, rate limits (max 10 concurrent), and read-only safe-to-retry nature.

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?

Efficiently structured with summary, guidelines, auth note, Args, Returns, Example. Every sentence adds value, no 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?

Despite simplicity (2 params, no nested objects), description covers purpose, usage, behavior, parameters, and return format (with matching output schema). Complete and self-contained.

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 coverage 0%, but description explains both parameters in Args with examples and sources (list_audiences, list_segments), adding meaning beyond name/type.

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?

Clearly states verb 'Retrieve' and resource 'full details of a specific segment including member count and filter conditions'. Distinguishes from siblings by referencing list_segments and list_segment_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 says when to use (inspect conditions, verify type/member count) and provides alternatives (list_segments to browse, list_segment_members for individuals).

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