Skip to main content
Glama

Resolve Audience Segment

resolve_segment
Read-onlyIdempotent

[Read · free] Resolve an audience segment into a concrete list of person_ids. For manual / auto_stream segments, returns stored members. For smart segments, evaluates the segment's config predicate (title_contains / company_contains) and returns matches ordered by engagement with your posts. Smart segments only match people connected to you: people who engaged with posts you can see in Flux (your own profile, tracked/monitored profiles, and posts you collected) and people in your campaigns' constellations. Free — costs 0 credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "segment_id": "<segment_id>"
    },
    "name": "resolve_segment"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax person_ids to return (default 1000)
segment_idYesSegment id (from list_segments / create_segment)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the description earns credit for what it adds on top: zero credit cost, the distinct resolution paths per segment type, and the predicate fields (title_contains / company_contains) that smart segments evaluate. Most importantly it discloses the matching boundary — smart segments only surface people connected to you (visible-engagement and campaign constellations) — which is a result-set restriction an agent cannot learn from the annotations or schema.

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 the operation and cost tag, then layered behavior by segment type — a sensible ordering with no filler sentences. The closing 'Free — costs 0 credits' restates the '[Read · free]' marker at the start, a minor redundancy in an otherwise dense block.

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?

For a two-parameter read tool with no output schema, the description supplies everything an agent needs: the return type (person_ids), ordering semantics, the credit cost, and the eligibility boundary on smart segments. Nothing material is missing for correct invocation or interpretation of results.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description rises above it by explaining that the referenced segment resolves differently depending on its type, and that smart results come back 'ordered by engagement,' which explains which results survive the limit cap. It does not discuss the limit range or what happens when the cap truncates, leaving a small gap.

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?

Opens with a specific verb plus resource plus output: 'Resolve an audience segment into a concrete list of person_ids.' It goes further and splits the behavior by segment kind (manual / auto_stream vs. smart), which tells an agent exactly what it will get back. The resource is unambiguously a segment rather than a collection, so it is separable from resolve_collection.

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

Usage Guidelines4/5

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

The context for calling it is clear: you have a segment_id and need person_ids. The schema points at list_segments / create_segment as the source of the id. However, it never states when not to use it, nor explicitly contrasts it with resolve_collection for the collection analogue, so the routing guidance stops short of explicit alternatives.

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