Skip to main content
Glama
Sign In
Arsel MCP Server

Arsel MCP Server

Official
by Arsel-SA
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Segments

list-segments
Read-onlyIdempotent

Retrieves audience segments with filter rules, status, and contact counts so you can inspect dynamic audiences and target campaigns. Supports name search and cursor pagination.

Instructions

List segments with their rules and contact counts. Segments are dynamic audiences: a filter of rules decides who is in, and campaigns target them through segment_ids. status is processing while the members are being computed and ready after. contact_count is as of counted_at, and null while the segment is processing. Don't read ids or timestamps back to the user unless they ask for them.

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
afterNoCursor for the next page: the `id` of the last item on this page. Cannot be combined with `before`.
limitNoItems per page, 1-100. Defaults to 20.
beforeNoCursor for the previous page: the `id` of the first item on this page.
searchNoCase-insensitive search by segment name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world semantics, so the description is not needed for safety. It instead discloses output behaviour the annotations cannot: the processing/ready status lifecycle, contact_count being a snapshot as of counted_at, and it being null while processing — genuinely useful for interpreting results. It stops short of describing pagination behaviour or ordering.

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?

Purpose is front-loaded in the first clause, then each subsequent sentence adds a distinct piece of information (segment definition, status lifecycle, count freshness, presentation rule). No repetition or filler, though the presentation instruction sits after the technical details rather than being grouped with output guidance.

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?

With no output schema, the description does the work of explaining the key returned fields (filter, segment_ids, status, contact_count, counted_at), which is the main completeness need. Minor gaps remain: how pagination metadata is returned and whether segments are ordered, neither of which the description or an output schema covers.

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?

The description never mentions the pagination or search parameters; it only discusses returned fields. Schema coverage is 100% and each parameter has its own description, so the baseline of 3 applies and the description neither compensates nor overrides.

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?

Opens with a specific verb and resource plus the payload it returns: 'List segments with their rules and contact counts.' The follow-up sentence defines what a segment is, which an agent could not infer from the name alone; only sibling differentiation is absent, but no other segment-listing tool exists in the catalog.

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 implied by the resource (read segments to see rules and audience size) but there is no explicit statement of when to call this versus e.g. list-lists or get-list, and no exclusions or prerequisites. Adequate but relies on the agent inferring intent from the domain explanation.

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

Deploy Server

Other Tools