Skip to main content
Glama

extract_youtube_transcript

Read-only

Extract YouTube video transcripts with timestamps, language preferences, and translation. Supports fallback crawling and saving full transcript to markdown files.

Instructions

Extract YouTube transcripts with timestamps. Works with public captioned videos. Supports fallback to page crawl. Use output_path to persist the full unsliced transcript to disk as markdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesYouTube video URL
languagesNoLanguage codes in preference order
translate_toNoTarget language for translation
include_timestampsNoInclude timestamps
preserve_formattingNoPreserve formatting
include_metadataNoInclude video metadata
auto_summarizeNoAuto-summarize large content
max_content_tokensNoMax tokens before summarization
summary_lengthNo'short'|'medium'|'long'medium
llm_providerNoLLM provider
llm_modelNoLLM model
enable_crawl_fallbackNoEnable page crawl fallback when API fails
fallback_timeoutNoFallback crawl timeout in seconds
enrich_metadataNoEnrich metadata (upload_date, view_count) via page crawl
content_offsetNoStart position for content (0-indexed)
content_limitNoMax characters to return (0=unlimited)
output_pathNoAbsolute file path (auto .md extension) to persist the full unsliced transcript. When set, the response is slimmed to metadata+file path. content_limit/content_offset still affect the response copy but not the on-disk file.
include_content_in_responseNoWhen True (with output_path set), keep the transcript in the response too. Note: the response copy is still subject to content_limit/content_offset slicing; only the on-disk file holds the full transcript. Defaults to False.
overwriteNoOverwrite an existing output file at output_path. Defaults to False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description adds value beyond annotations (readOnlyHint: true) by disclosing fallback crawling behavior, output_path persistence, metadata enrichment, and auto-summarization. No contradictions found. Could mention rate limits or video length constraints.

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 sentences, front-loaded with the core purpose. Each sentence adds distinct information: extraction, constraints, fallback, output guidance. Slightly verbose but no redundancy.

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?

Given the tool's complexity (19 params, output schema exists), the description covers key behaviors: extraction, fallback, output persistence, summarization, metadata enrichment. It omits rate limits and language constraints but the schema covers languages. Output schema reduces need to describe return values.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 19 parameters have schema descriptions (100% coverage), and the description adds context for output_path (persist full unsliced transcript as markdown) and fallback. The description does not override schema but complements it effectively.

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 clearly states the tool extracts YouTube transcripts with timestamps, specifying the resource (YouTube) and action (extract). It distinguishes from siblings like get_youtube_video_info (video metadata) and batch_extract_youtube_transcripts (batch variant).

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

Usage Guidelines4/5

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

The description provides context: works only with public captioned videos, supports fallback to page crawl, and suggests using output_path for persistence. However, it does not explicitly compare to sibling tools like extract_youtube_comments or state when to avoid using this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/walksoda/crawl-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server