Skip to main content
Glama

get_segment_members

Retrieve members from a specific Mailchimp audience segment to manage targeted communications and analyze subscriber groups.

Instructions

List members in a specific segment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYes
segment_idYes
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Handler function for 'get_segment_members' tool which fetches member data from a specific Mailchimp segment.
    async def get_segment_members(
        list_id: str,
        segment_id: str,
        count: int = 20,
        offset: int = 0,
    ) -> str:
        """List members in a specific segment."""
        mc = get_client()
        data = await mc.get(
            f"/lists/{list_id}/segments/{segment_id}/members",
            params={"count": min(count, 100), "offset": offset},
        )
        members = []
        for m in data.get("members", []):
            members.append({
                "email": m.get("email_address", ""),
                "full_name": m.get("full_name", ""),
                "status": m.get("status", ""),
            })
        return _fmt({"total_items": data.get("total_items", 0), "members": members})
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic operation. It doesn't disclose behavioral traits like pagination behavior (implied by count/offset but not explained), rate limits, authentication needs, error conditions, or what 'members' entails (e.g., contact details). The description is minimal and lacks critical operational context.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose, making it easy to scan and understand at a glance, though this brevity contributes to gaps in other dimensions.

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?

Given the tool has an output schema (which should cover return values), the description's minimalism is partially offset. However, for a tool with 4 parameters, 0% schema coverage, and no annotations, the description is inadequate—it doesn't explain key aspects like pagination, data scope, or error handling, leaving significant gaps for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 but adds no parameter information. It doesn't explain what 'list_id' or 'segment_id' refer to, how to obtain them, or the semantics of 'count' and 'offset' for pagination. The description fails to provide meaning beyond the bare schema, leaving parameters largely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List members in a specific segment' clearly states the action (list) and target resource (members in a segment). It distinguishes from general 'list_members' by specifying segment context, though it doesn't explicitly differentiate from 'search_members' or 'get_member' which might overlap in functionality.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'list_members', 'search_members', or 'get_member'. The description implies segment-specific listing but doesn't clarify prerequisites, exclusions, or comparative use cases with sibling 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/AlexlaGuardia/mcp-mailchimp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server