Skip to main content
Glama

Development Radio

Get one episode's timed transcript

get_transcript
Read-only

Returns one episode's full timed transcript as Markdown, with speaker names and HH:MM:SS timestamps, preceded by its title, page URL and the primary sources it cites. Use this when you need exact wording, or to quote or locate a passage; get_episode is shorter when a summary is enough. The speakers, Maya and Alex, 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_transcript"
  }
}

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

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a pure read. Beyond that it discloses the response shape (Markdown body, speaker names, HH:MM:SS timestamps, title/URL/sources preamble) and a genuinely useful caveat that the speakers are AI-generated voices, which matters for quoting. It stops short of saying anything about transcript length, truncation, or pagination for long episodes.

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?

Three sentences, front-loaded with the return payload, then the use case and alternative, then a short caveat. No filler and nothing repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description supplies the content and format of the return value, the decision rule versus the sibling summary tool, and a caveat about synthetic speakers. Nothing an agent needs in order to call it or interpret the result is missing.

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 coverage is 100%: the single id parameter is documented in the schema with its source tools and a concrete example value. The description adds no additional meaning about id, so the schema carries the full burden and 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?

"Returns one episode's full timed transcript as Markdown" gives a specific verb, resource, and output format, then details the payload (speaker names, HH:MM:SS timestamps, title, page URL, cited sources). It also distinguishes itself from get_episode, which returns a summary, so an agent can pick correctly without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ("when you need exact wording, or to quote or locate a passage") paired with an explicit alternative and the condition that selects it ("get_episode is shorter when a summary is enough"). The routing decision is fully determined by the description.

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.