Skip to main content
Glama

List episodes

list_episodes
Read-onlyIdempotent

List a show's episodes, newest first, with episode_slug, publish date and fact count. Pages via offset/next_offset.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "show": "<show>"
    },
    "name": "list_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
showYesShow slug (such as huberman-lab) or show title (such as "Huberman Lab"), from list_shows or a search result's show_slug
limitNoHow many to return, 1-100, default 25
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.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds real context beyond that: the result ordering (newest first) and the pagination mechanism via next_offset, which an agent needs to page correctly.

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?

A single tight sentence plus a short paging clause; ordering and returned fields are front-loaded with no filler wording.

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?

The tool is simple and an output schema exists, so return values need not be spelled out. Ordering, scoping and pagination are all addressed; only explicit routing versus siblings like search or get_episode is absent.

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 all three parameters are already documented in the schema, including next_offset paging. The description only restates the paging pattern without adding range, default, or format detail beyond the schema — the baseline 3 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 a show's episodes) and adds ordering (newest first) plus the fields returned. It implicitly separates itself from get_episode by framing the result as a collection scoped to a show, but it never names an alternative the way a 5 would.

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?

The mention of paging via offset/next_offset implies this is the collection-browsing tool, but there is no explicit 'use this when' or 'use search/get_episode instead when' statement. Usage is inferable rather than stated.

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