Skip to main content
Glama

TranscriptLab

Get YouTube transcript

transcriptlab_get_transcript

Get a YouTube transcript from existing captions. Use when the user gives a YouTube link or video ID and wants the transcript. Returns the transcript, or a job id when the request outlives the synchronous window: if a job comes back, poll transcriptlab_get_job_status, then read the text with transcriptlab_retrieve_transcript. The first delivery of each transcript variant can spend credits; later deliveries of that variant are free. Captions only: when the user asks which caption tracks exist use transcriptlab_discover_captions; when the video has no captions, or the source is an attached file or a direct media link, use transcriptlab_transcribe_file or transcriptlab_transcribe_media_url.

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

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL or 11-character video ID.
alsoNoAdditional formats to include in a JSON response.
langNoCaption language. Omit it to get the video's own language (recommended); set it only to request a specific language.
typeNoCaption track type; defaults to any.
formatNoOutput format; defaults to json.
cleanupNoStrip filler words and stray timestamps from the caption text.
metadataNoInclude video metadata when available; defaults to true.
translateNoTranslate captions to this language when available.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false, which would leave the agent guessing why it isn't a pure read. The description explains the synchronous window, the job-id fallback with the exact follow-up chain, and the credit model (first delivery of a variant costs credits, later ones free) — context the structured fields cannot convey.

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?

Front-loaded with purpose and trigger, then routing, then async/credits, then exclusions — a logical order with no filler. It is fairly dense with chained clauses and could be broken into shorter sentences for scanability.

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?

With 8 parameters and no output schema, the description still covers what comes back (transcript or job id) and what to do in each case, plus cost implications. An agent can invoke it and handle both outcomes without further inference.

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 url, also, lang, type, format, cleanup, metadata, and translate are all documented in the schema itself. The description adds no parameter-level detail beyond the implicit "captions only" scope, so this sits at the baseline.

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 ("Get a YouTube transcript") plus the source constraint ("from existing captions"), which immediately separates it from the transcription siblings that handle files and direct media links.

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 the trigger condition (user supplies a YouTube link or video ID and wants the transcript), then explicitly routes three excluded cases: caption-track discovery to transcriptlab_discover_captions, and no-captions/file/direct-link cases to transcriptlab_transcribe_file or transcriptlab_transcribe_media_url.

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.