Skip to main content
Glama

Get one episode's notes and sources

get_episode
Read-only

Returns one episode's show notes: summary, takeaways, the check the episode suggests running, chapters with timestamps, topics, every primary source it cites (title and URL), and links to the page, the MP3 and the YouTube video when there is one. Use this when you have an episode id and need its findings and sources without the full transcript. The show's hosts are AI-generated voices.

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": {
      "id": "<id>"
    },
    "name": "get_episode"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEpisode id as returned by search_episodes or list_episodes, for example 2026-11-20-nginx-five-teams-daily.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description's added value is payload detail plus the conditional disclosure that a YouTube link exists only 'when there is one'. It says nothing about behavior on an unknown id (error vs. empty), payload size, or whether notes reflect a mutable source, which would be the higher-value additions for a read tool.

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 sentences, front-loaded with the return payload and followed by the usage rule, with no filler in the routing sentence. The closing note that hosts are AI-generated voices is a provenance caveat rather than invocation guidance, so it is slightly tangential but still cheap and potentially useful for how the agent presents the content.

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?

With no output schema, the description carries the burden of explaining return contents and does so thoroughly, covering every major field and conditional links. It lacks only edge-case behavior for a bad or missing id, which is the remaining gap for a single-parameter read tool.

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 description coverage is 100% and the single parameter already documents the id format and its origin tools (search_episodes, list_episodes), so the schema does the heavy lifting. The description adds only 'you have an episode id', which is no more than the schema states, so the baseline 3 applies.

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?

The description uses a specific verb ('Returns') plus resource ('one episode's show notes') and then enumerates the exact payload: summary, takeaways, suggested check, chapters with timestamps, topics, primary sources with title and URL, and page/MP3/YouTube links. 'without the full transcript' implicitly but clearly separates it from get_transcript, so an agent can pick the right tool 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?

It states the precondition ('when you have an episode id') and the selection condition ('need its findings and sources without the full transcript'), which effectively routes transcript-only needs to get_transcript. It stops short of naming that sibling explicitly or saying when not to use this tool (e.g., bulk listing via list_episodes/search_episodes).

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.