Skip to main content
Glama

Get podcast episode detail

get_podcast
Read-onlyIdempotent

Podcast detail, duration, audio file and citation link; says which model generated the transcript. Transcript is opt-in, bounded and pageable.

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_podcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPodcast id from search_podcasts, e.g. 39121, or podcast:39121
include_similarNoAdd up to 5 similar records, each explained
transcript_offsetNoStart offset into the transcript (chars), with include_transcript
include_transcriptNoDefault false — set true to include the transcript text
transcript_max_charsNoMax transcript characters to return (default/max 25000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / include_similar
      Added value: +{
      +  "description": "Add up to 5 similar records, each explained",
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / transcript_max_chars / maximum
      Removed value: -9007199254740991
    • removedInput schema / properties / transcript_offset / maximum
      Removed value: -9007199254740991
  3. Changed3 schema fields changed
    • addedInput schema / properties / id / anyOf
      Added value: +[
      +  {
      +    "maxLength": 1000,
      +    "type": "string"
      +  },
      +  {
      +    "type": "number"
      +  }
      +]
    • changedInput schema / properties / id / description
      Previous value: -"Podcast id from search_podcasts, e.g. 39121"New value: +"Podcast id from search_podcasts, e.g. 39121, or podcast:39121"
    • removedInput schema / properties / id / type
      Removed value: -[
      -  "string",
      -  "number"
      -]
  4. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the transcript is off by default, size-bounded, and pageable, and the payload discloses which model produced the transcript. That is useful context an agent cannot get from the annotations alone.

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 dense sentences with no filler; the returned-field inventory comes first and the transcript constraint second, which is the right order. The first clause is a telegraphic noun list ('Podcast detail, duration, audio file and citation link') that reads slightly clipped but wastes nothing.

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 telling the agent what comes back, and it does list the main payload elements plus the conditional transcript. Combined with full schema coverage on five parameters, an agent has enough to call this correctly; only error or empty-result behavior is unaddressed.

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%, so all five parameters including include_transcript, transcript_offset, and transcript_max_chars are already documented in structured form. The description echoes the opt-in/bounded/pageable semantics without adding syntax, format, or interaction details beyond the schema, so the baseline of 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 the resource (podcast) and enumerates what the response carries: detail, duration, audio file, citation link, transcript generator model. That is concrete and lets an agent distinguish it from get_video or get_publication by resource type. It does not explicitly contrast itself with a sibling, so it stops short of 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: 'Transcript is opt-in' signals that the default call is a lightweight metadata fetch and that transcript retrieval is a deliberate choice. There is no explicit when-to-use/when-not statement and no pointer to search_podcasts as the discovery step, even though the schema references it.

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.