Skip to main content
Glama

Get transcript

get_transcript
Read-onlyIdempotent

Get a transcript with speakers and timestamps, up to 40 paragraphs (about 12k characters) per page. total is the paragraph count; pass next_offset as offset for the next page.

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

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
limitNoMost paragraphs per page, 1-80, default 40. A page also stops at about 12k characters of text.
offsetNoFirst paragraph to return, default 0. Use next_offset from the previous page, or a search_transcripts result's paragraph.
episodeYesEpisode slug: episode_slug from list_episodes or a search result

Output Schema

NameRequiredDescriptionDefault
urlYes
noteNo
showYes
titleYes
totalNo
offsetNo
show_slugYes
paragraphsYes
source_urlNo
next_offsetNo
episode_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower, and the description still adds real context: a page is capped at roughly 40 paragraphs / 12k characters, and the response's total is a paragraph count. It stops short of noting whether the page cap is a hard limit or how truncation is signalled, but the pagination contract is well disclosed.

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?

Two sentences, front-loaded with the purpose and the page size, then the pagination instruction. Every clause carries information and nothing is repeated 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?

With an output schema present, return values need not be spelled out, and the description instead covers the one thing the schema cannot: the pagination loop of total plus next_offset feeding the next offset. What remains missing is only guidance on choosing this tool over search_transcripts, which is a selection concern rather than a completeness gap in the call itself.

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 the schema already documents show, episode, limit, and offset thoroughly, including "Use next_offset from the previous page." The description reinforces the offset/next_offset relationship and ties total to paragraph count, but adds little beyond the structured fields, which is the expected baseline here.

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 opens with a specific verb and resource ("Get a transcript") and immediately states the content and fidelity of the result: speakers and timestamps. It is clear what the tool returns, but it never names or contrasts a sibling such as search_transcripts, so an agent must infer the distinction between fetching a full transcript and searching one.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: nothing indicates that this is the tool for retrieving a full episode transcript versus search_transcripts for locating a passage. The only procedural advice concerns paging ("pass next_offset as offset"), which is invocation mechanics rather than tool selection.

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