Skip to main content
Glama

List Audience Segments

list_segments
Read-onlyIdempotent

[Read · free] List all audience segments for the authenticated user, with member counts. Audience segments are named groups of people (e.g. 'ICP — VPs of Marketing', 'Champions'). Free — costs 0 credits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_segments"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional filter by segment type ('manual', 'smart', or 'auto_stream')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real context beyond them: that the call is free (0 credits), which matters in a toolset that also exposes get_credit_balance and get_cost_estimate, and that member counts come back in the response.

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?

Front-loaded with a useful '[Read · free]' tag, then purpose, then a clarifying definition. The closing 'Free — costs 0 credits' partially repeats the header tag, a small redundancy, but overall it is short and well ordered.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter read tool with full schema coverage and no output schema, the description covers purpose, cost, and the shape of the result (segments with member counts). Only the type-filter behavior and pagination/limits are unaddressed.

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 description coverage is 100% and the single 'type' parameter documents its three enum values in the schema. The description adds nothing about filtering by segment type, so the baseline 3 applies — the schema does all the parameter work.

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?

States a specific verb and resource ('List all audience segments') plus scope ('for the authenticated user') and return content ('with member counts'). It even defines what a segment is with examples, which conceptually separates it from segment-template siblings, but it never explicitly contrasts with list_segment_templates or list_collections.

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?

Usage is only implied — an agent can infer this is the discovery step before add_to_segment or create_segment, but the description never says when to call it, what prerequisite it serves, or when another list tool is the better choice. No exclusions or alternatives are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources