Skip to main content
Glama

Get Transcript

get_transcript

Extract transcript text from a YouTube video by URL or video ID. Choose language and optionally include timestamps for captions and analysis.

Instructions

Get transcript text from a YouTube video.

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": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube URL or video ID
languageNoLanguage code (default: auto-detect)auto
with_timestampsNoInclude timestamps in output

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.4
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / language / description
      Added value: +"Language code (default: auto-detect)"
    • addedInput schema / properties / url / description
      Added value: +"YouTube URL or video ID"
    • addedInput schema / properties / with_timestamps / description
      Added value: +"Include timestamps in output"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does not say what happens when a video has no captions, whether transcripts are auto-generated or human-authored, how 'auto-detect' language fallback behaves, or whether any quota/auth constraints apply.

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?

It is a single front-loaded sentence with zero waste and no padding. Its brevity is genuine conciseness rather than rambling, though it borders on under-specification for a tool with three parameters.

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

Completeness2/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 values need not be explained, but the description omits the tool's most important operational caveat for a transcript fetcher: behavior when captions are unavailable or language detection fails. For a 3-parameter tool with no annotations, more behavioral context is expected.

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, language, and with_timestamps are already fully documented in the schema. The description adds no additional meaning about formats or defaults, so the baseline 3 applies.

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 names a specific verb and resource ('Get transcript text') scoped to a specific source ('from a YouTube video'), which clearly separates it from the sibling get_video_info by resource type. It stops short of explicitly naming that sibling, so it does not fully earn a 5.

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 statement of when to use this versus get_video_info, nor any precondition such as whether the video must have captions enabled. The only implied guidance comes from the resource name itself.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools