Skip to main content
Glama

Get a transcript

get_transcript
Read-onlyIdempotent

Timestamped transcript of an indexed or ingested item, paginated (~30k characters per page). If it returns not_ingested, call ingest first. Prefer search/get_passage when you only need part of it. Costs 0.2 credits per page. For a summary or key points of one specific YouTube video, call show_player first with a short summary and the key points as moments, then write your answer citing timestamps.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoItem id from search/discover/list_episodes, e.g. "yt:dQw4w9WgXcQ"
urlNoAlternatively, a YouTube or podcast episode URL
cursorNonext_cursor from the previous page
formatNotext = "[M:SS] line" text; segments = structured array with deep linkstext
max_charsNo

Output Schema

NameRequiredDescriptionDefault
itemYesA piece of media. Pass `id` to get_transcript, get_passage or ingest.
pageYes
textNo
qualityNo
segmentsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds what they cannot: page size (~30k chars), the cursor-based pagination model, a cost of 0.2 credits per page, and a named failure mode (not_ingested) with the recovery step. That is substantive operational context beyond structured fields.

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?

Four sentences, each carrying distinct load: what it returns, the pagination/cost model, the failure fallback, and the sibling routing. The scoping information is front-loaded and there is no filler or restatement of the name.

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?

An output schema exists so return structure need not be described, and the description nonetheless covers the pieces an agent needs before calling: pagination behavior, cost, ordering/format expectations, error recovery, and alternatives. Nothing material is missing for a zero-required-parameter read tool.

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 80%, so id, url, cursor, and format are already documented in the schema; the description only reinforces the page-size semantics behind max_chars and the fact that cursors come from prior pages. It adds little field-level meaning the schema does not already carry, so the baseline of 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?

The description names a specific resource (timestamped transcript of an indexed/ingested item) and immediately distinguishes it from siblings by assigning partial-content needs to search/get_passage and summaries to show_player. An agent can identify what this returns and when it is the wrong tool without reading any 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 routing is given in both directions: prefer search/get_passage when only part is needed, call ingest first on a not_ingested result, and use show_player for a summary of one YouTube video. Each alternative is tied to a concrete condition rather than left to inference.

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