Skip to main content
Glama
Podcast MCP
by calebn

segment_list_tool

List the newest version of each saved intro, outro, sponsor read, or sting in a per-user segment library, including damaged versions with error details.

Instructions

List the segment library: the newest version of each saved intro, outro, sponsor read or sting.

A segment whose newest version is damaged is listed as {"id", "version", "damaged": true, "problem", "code"} rather than hidden. Read-only; the library is per user, not per episode.

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": "segment_list_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it declares the operation read-only, clarifies the library is per user rather than per episode, and discloses the non-obvious behavior that damaged segments are surfaced with a specific shape instead of hidden. It stops short of covering ordering, result size, or pagination.

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?

Three short sentences, front-loaded with the primary action and scope, then the damaged-segment edge case, then the read-only/per-user caveat. Nothing is repeated from structured fields and no sentence is filler.

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 zero-parameter list tool with an output schema, the description covers the essential surprises: read-only status, per-user scope, and the damaged-segment record shape. Minor gaps around ordering and result volume are the only thing an agent might still wonder about.

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?

The tool takes zero parameters, so there is no parameter meaning to add; baseline applies.

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?

The description names a specific verb and resource ('List the segment library') and pins down the exact scope: the newest version of each saved intro, outro, sponsor read or sting. That scope implicitly separates it from per-segment tools like segment_show_tool, though no sibling is named explicitly.

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 browse-the-library call, but the description never states when to choose it over segment_show_tool or the various list_* siblings, and gives no exclusions or prerequisites.

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