Skip to main content
Glama

get_youtube_video_info

Read-only

Extract YouTube video metadata and transcript availability. Optionally summarize the transcript and persist it as markdown to disk.

Instructions

Get YouTube video metadata and transcript availability. Use output_path to persist the full transcript to disk as markdown and receive a slim response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_urlYesYouTube video URL
summarize_transcriptNoSummarize transcript
max_tokensNoToken limit for summarization
llm_providerNoLLM provider
llm_modelNoLLM model
summary_lengthNo'short'|'medium'|'long'medium
include_timestampsNoInclude timestamps
output_pathNoAbsolute file path (auto .md extension) to persist the full video info + transcript as markdown. When set, the response is slimmed to metadata+file path.
include_content_in_responseNoWhen True (with output_path set), also include the full transcript in the response. 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?

Annotations declare readOnlyHint=true. The description adds that persisting to disk writes to a local file and alters response format. This provides behavioral context beyond the annotation, though the side effect of file writing is still safe.

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?

Two concise sentences, front-loaded with purpose and key option. No unnecessary words.

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?

Description covers core purpose and one key parameter, but with 10 parameters and sibling tools, more context on summarization and differentiation would be beneficial. Output schema covers return values, so not necessary in description.

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 100%, so parameters are well-documented. The description adds value for output_path by explaining its effect on response, but other parameters like summarize_transcript are not elaborated beyond schema defaults.

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 clearly states the tool retrieves video metadata and transcript availability, and mentions persisting transcript to disk. Verb 'Get' is specific. However, it does not explicitly differentiate from sibling tools like extract_youtube_transcript.

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?

The description hints at using output_path but provides no guidance on when to use this tool versus alternatives like extract_youtube_transcript. No context on exclusions or prerequisites.

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