Skip to main content
Glama

TranscriptLab

Retrieve completed transcript

transcriptlab_retrieve_transcript

Read a YouTube transcript that is already published for this account, without starting a new fetch. Use it after transcriptlab_get_job_status reports a job done, or to re-open a variant that was delivered before. For a first request use transcriptlab_get_transcript instead. Reading an already delivered variant is free; a never-before-delivered variant can spend credits like the original request.

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": {
      "url": "<url>"
    },
    "name": "transcriptlab_retrieve_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL or 11-character video ID.
langNoCaption language. Omit it to get the video's own language (recommended); set it only to request a specific language.
typeNo
formatNo
cleanupNo
metadataNo
translateNoTranslation target, if requested for the original fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: it explains the billing asymmetry (already-delivered variants are free, a never-delivered variant can spend credits), which is the reason readOnlyHint=false despite the 'Read' framing. It does not say what happens when no transcript exists yet (error vs. auto-fetch) or what the returned payload looks like, so it stops short of full behavioral disclosure.

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?

Four short sentences, front-loaded with the core definition, then the sequencing guidance, then the alternative, then cost. The cost sentence is slightly wordy but earns its place by explaining the surprising non-read-only annotation.

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

Completeness3/5

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

For a 7-parameter tool with 43% schema coverage and no output schema, the description covers the routing question well but leaves half the parameters and the failure/empty-result behavior unexplained. Adequate for choosing the tool, thin for invoking it correctly with non-default options.

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 only 43%, so the description needs to compensate but largely does not: type, format, cleanup, metadata, and translate are undocumented in both places. It only implicitly gestures at 'variant' and language selection via the mention of re-opening a delivered variant.

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?

States a specific verb and resource ('Read a YouTube transcript') plus a precise scope qualifier: 'already published for this account, without starting a new fetch.' This cleanly separates it from transcriptlab_get_transcript, which the description explicitly names as the first-request path.

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?

Gives explicit when-to-use conditions (after transcriptlab_get_job_status reports done, or to re-open a previously delivered variant) and an explicit when-not-to-use with the named alternative ('For a first request use transcriptlab_get_transcript instead'). Nothing is 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.