Skip to main content
Glama

Get episode

get_episode
Read-onlyIdempotent

Get an episode's summary, publish date, named speakers and every sourced fact with quote and timestamp.

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

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
episodeYesEpisode slug: episode_slug from list_episodes or a search result

Output Schema

NameRequiredDescriptionDefault
urlYes
showYes
factsYes
titleYes
durationNo
overviewNo
speakersYes
publishedNo
show_slugYes
source_urlNo
episode_slugYes
published_tsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results include sourced facts with quotes and timestamps, useful context on data richness, but says nothing about missing episodes, error behavior, or payload size.

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 front-loaded sentence with no filler; every clause names a returned artifact. Nothing is repeated and nothing is wasted.

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 two-parameter read tool with full schema coverage, annotations, and an output schema, the description is adequate. The returned-field enumeration is somewhat redundant with the output schema, but it still helps an agent decide the tool fits its need.

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 both parameters are fully documented in the schema including their source (list_shows, list_episodes, search results). The description adds no parameter meaning beyond that, so 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 gives a specific verb ('Get') and resource ('an episode') and enumerates what comes back – summary, publish date, speakers, sourced facts with quote and timestamp – which makes it distinguishable from get_transcript or get_topic by content. It stops short of naming a sibling explicitly, so it is not a 5.

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 detail lookup for a specific episode identified by show and episode slug. There is no statement of when to prefer this over get_transcript, get_topic, or search, and 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources