Skip to main content
Glama

List shows

list_shows
Read-onlyIdempotent

List shows with their slug, host and episode count, 25 per page by title. Filter with query; descriptions are shortened.

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_shows"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return, 1-100, default 25
queryNoPart of a show's title, slug, host or description, case-insensitive (such as "health" or "Lex")
offsetNoHow many to skip, default 0. Pass next_offset from the previous page to get the next page.

Output Schema

NameRequiredDescriptionDefault
totalYes
offsetYes
resultsYes
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, non-destructive behavior, so the bar is lower. The description still adds real context beyond them: a fixed 25-per-page paging model, a title sort order, and the caveat that descriptions are shortened, which warns the agent not to rely on full description text.

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?

Two dense sentences with the return fields and paging model front-loaded and no filler. The phrase '25 per page by title' is slightly ambiguous in reading (page size vs. sort), which keeps it short of a 5.

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 simple read-only list tool with an output schema, full schema coverage and complete annotations, this is close to sufficient: shape, paging and the shortened-description caveat are all covered. Only the absence of routing guidance to sibling search tools leaves a gap.

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 coverage is 100%, so the schema already documents limit, query and offset with examples and the next_offset paging hint. The description only really adds the sort order ('by title'); its '25 per page' restates the limit default, so it does not materially extend parameter meaning.

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?

States a specific verb and resource ('List shows') plus exactly what each row contains (slug, host, episode count), the sort order (by title) and the page size. The resource 'shows' is distinguishable from the sibling set (episodes, topics, transcripts) without opening a schema, though the description never explicitly contrasts itself with them.

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?

'Filter with query' implies when the query parameter is useful, but there is no guidance on when to prefer this listing over siblings such as search or search_transcripts, and no exclusion conditions. Usage must be largely inferred.

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