Skip to main content
Glama

List channel or show episodes

list_episodes
Read-onlyIdempotent

Latest uploads of a YouTube channel (handle like "@lexfridman", channel URL, or UC… id) or episodes of a podcast (RSS feed URL, Apple Podcasts show URL, or Spotify show URL). Newest first. Pass an episode's url to ingest.

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": {
      "source": "<source>"
    },
    "name": "list_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sourceYesChannel handle/URL/id, RSS feed URL, Apple Podcasts or Spotify show URL

Output Schema

NameRequiredDescriptionDefault
sourceYes
episodesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive behavior, so the bar is lower. The description adds genuinely useful behavior beyond them: results are ordered 'newest first', and it explains the downstream handoff to `ingest`. It does not mention pagination, rate limits, or what happens when a source has no episodes.

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?

Three tight sentences with the core purpose front-loaded and the chaining hint last. Nothing is redundant. Minor cost for the cryptic 'UC… id' phrasing, which is informative but requires prior knowledge of YouTube channel ID prefixes.

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 described here. For an open-world listing tool spanning four source platforms, the description covers source formats, ordering, and the follow-up action adequately. The only real gap is the unexplained `limit` control and the absence of guidance on multi-platform source ambiguity.

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?

Schema coverage is 50%, so the description must compensate somewhat and largely does: it names concrete accepted formats for `source` (handle like "@lexfridman", channel URL, UC… id, RSS, Apple Podcasts, Spotify show URL) that go beyond the terse schema string. However, the `limit` parameter is never explained — its purpose, units, or the default of 15 are left entirely to the schema.

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?

Specific verb and resource: lists latest uploads of a YouTube channel or episodes of a podcast, with the accepted source forms enumerated. It is clear enough to distinguish from `ingest` (which it points to) but does not explicitly distinguish itself from `list_channels`, which also deals with channels.

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?

The closing sentence 'Pass an episode's `url` to ingest' establishes the intended workflow and makes clear this is the discovery step before ingestion. There are no explicit exclusions or named alternatives for when a different listing tool would be preferable, so it stops short of a 5.

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