Skip to main content
Glama

List Segment Templates

list_segment_templates
Read-onlyIdempotent

[Meta · free] List available smart-segment templates. Pass a template id to create_segment to pre-fill its config predicate without crafting one from scratch. Each template's description states exactly what its config matches; like every smart segment, it only matches people connected to you (engagers on your visible posts and people in your campaigns). 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_segment_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly/no-destructive/idempotent/closed-world, so the description correctly focuses on what they cannot convey: that the call is free (0 credits) and that every smart segment only matches people connected to the caller (engagers on visible posts, campaign people). It stops short of noting ordering or whether the list is exhaustive, but the scope caveat is the valuable disclosure.

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?

Four tight sentences, front-loaded with the purpose, then workflow, then semantics, then cost. The only waste is the cost note appearing twice — once in the '[Meta · free]' tag and again as 'Free — costs 0 credits' at the end.

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?

With no parameters and no output schema, the description carries the whole burden and does: what it returns, what each returned description means, how to use the result, and the cost. Nothing an agent needs to call it correctly is missing.

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?

Zero parameters, so the baseline is 4. The description still adds useful meaning about the shape of returned items — template ids and per-template descriptions that state what each config matches — which goes beyond the empty input schema.

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?

States a specific verb and resource ('List available smart-segment templates') plus the scope of what a template is. It also names the downstream consumer (create_segment) that distinguishes it from list_segments, so an agent can pick it without opening a schema.

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?

Explicitly tells the agent the intended workflow: take a template id and pass it to create_segment to pre-fill its config predicate 'without crafting one from scratch'. That names the alternative being avoided, though there is no explicit when-not-to-use or precondition statement.

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