Skip to main content
Glama

Get Episode

get_episode
Read-onlyIdempotent

Get one episode and its chapter metadata by slug.

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

Input Schema

NameRequiredDescriptionDefault
slugYes

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes
operationYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / meta / properties / clip_catalog
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "catalog_id": {
      +      "const": "htrtf-youtube-clips",
      +      "type": "string"
      +    },
      +    "catalog_sha256": {
      +      "pattern": "^[a-f0-9]{64}$",
      +      "type": "string"
      +    },
      +    "catalog_version": {
      +      "maxLength": 80,
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    "generated_at": {
      +      "format": "date-time",
      +      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "catalog_id",
      +    "catalog_version",
      +    "catalog_sha256",
      +    "generated_at"
      +  ],
      +  "type": "object"
      +}
  2. Changed36 schema fields changed
    • addedOutput schema / properties / data / properties / chapters / items / properties / end_ms / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / data / properties / chapters / items / properties / start_ms / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / data / properties / id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • addedOutput schema / properties / data / properties / publication_date / pattern
      Added value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    • removedOutput schema / properties / meta / properties / artifact_manifest_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / artifact_manifest_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / artifact_manifest_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / artifact_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / artifact_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / artifact_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / canonical_url / $ref
      Removed value: -"#/properties/data/properties/canonical_url"
    • addedOutput schema / properties / meta / properties / canonical_url / format
      Added value: +"uri"
    • addedOutput schema / properties / meta / properties / canonical_url / maxLength
      Added value: +2048
    • addedOutput schema / properties / meta / properties / canonical_url / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / release_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / release_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / release_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / rights / properties / policy_url / $ref
      Removed value: -"#/properties/data/properties/canonical_url"
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / format
      Added value: +"uri"
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / maxLength
      Added value: +2048
    • addedOutput schema / properties / meta / properties / rights / properties / policy_url / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / snapshot_sha256 / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / snapshot_sha256 / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / snapshot_sha256 / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / $ref
      Removed value: -"#/properties/meta/properties/manifest_sha256"
    • addedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / pattern
      Added value: +"^[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / artifact_manifest_hash / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / content_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / surface_version / properties / content_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / content_version / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / surface_version / properties / transcript_version / type
      Added value: +"string"
    • removedOutput schema / properties / meta / properties / transcript_version / $ref
      Removed value: -"#/properties/meta/properties/content_version"
    • addedOutput schema / properties / meta / properties / transcript_version / pattern
      Added value: +"^sha256:[a-f0-9]{64}$"
    • addedOutput schema / properties / meta / properties / transcript_version / type
      Added value: +"string"
  3. Changed1 schema field changed
    • addedOutput schema / properties / data / properties / person_role
      Added value: +{
      +  "enum": [
      +    "guest",
      +    "subject"
      +  ],
      +  "type": "string"
      +}
  4. 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 a closed-world scope, so the safety profile is fully covered without the description. The description's only added behavioral fact is that chapter metadata comes back with the episode; it says nothing about lookup failure behavior or access prerequisites.

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?

One short sentence with the verb, resource, identifier, and payload all front-loaded. Nothing in it is redundant or padded.

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 single-parameter read tool with annotations covering safety and an output schema covering the return shape, this is nearly complete. The remaining gap is the absence of any note on unknown-slug behavior, which is minor given the low complexity.

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?

There is a single parameter and schema description coverage is 0%, so the burden falls on the description. "By slug" does identify the parameter as a slug identifier, but it adds no format, casing, length, or example detail beyond what the schema's pattern and maxLength already constrain.

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 (get), a specific resource (one episode), and the lookup key (slug), plus the bonus payload (chapter metadata). It is clearly distinct from sibling resources such as get_clip or get_flashcards, though it does not name a sibling explicitly.

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: fetch a single episode when you have its slug. There is no explicit when-to-use/when-not guidance, no mention of what to call instead for listing or searching episodes, and no note on behavior when the slug is unknown.

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