Skip to main content
Glama
agentisend

agentisend

List contact segments

list_segments
Read-onlyIdempotent

View saved contact segments, their defining rules, and current matching member counts so you can review audience groups before planning a broadcast.

Instructions

Purpose: see the saved groups of contacts, the rules that define them, and how many people each currently matches. NOT for: sending to one. Who receives a broadcast is a person's decision. Returns: each segment with its rules and current size.

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
limitNoPage size (1-100).
cursorNonext_cursor from the previous page. Omit for the first page.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/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 safety behavior is fully covered. The description adds that segments carry their rules and a current match count (implying computed sizes), which is useful, but no pagination or freshness behavior is described beyond that.

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?

Structured as Purpose / NOT for / Returns, front-loading the core function and keeping every line informative. No filler or repetition.

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?

An output schema exists, so return values need not be spelled out, and the schema documents both pagination params. The description is nearly complete for a read-only list tool; it could note pagination usage but the schema already covers it.

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%; limit and cursor are fully documented in the schema. The description adds no parameter-level detail (page size limits, cursor reuse), so the schema does the heavy lifting and a baseline 3 is correct.

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?

The description gives a specific verb+resource ('see the saved groups of contacts') and enriches it with what each segment contains ('the rules that define them, and how many people each currently matches'). This clearly separates it from list_contacts, which lists people rather than rule-based groups.

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?

It includes an explicit 'NOT for: sending to one', which is a genuine exclusion, but the guidance is oblique and frames the negative around broadcast sending rather than distinguishing among the many list_* siblings. No alternative (e.g., list_contacts) is named for the adjacent use case.

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