ScriptHaul

Get YouTube transcript

get_transcript

Read-onlyIdempotent

Fetch the transcript of a single YouTube video by URL or 11-character video ID. Serves the permanent cache instantly when available and otherwise fetches from YouTube (uncached fetches are limited per IP per day). Formats: clean text, timestamped, both, srt, vtt, md, json.

Input Schema

TableJSON Schema

Name	Required	Description
`format`	No	Output format. Default "clean" (plain text). "timestamped" prefixes each line with a timestamp; srt/vtt are subtitle files; json is structured.
`language`	No	Preferred caption language code such as "en" or "pt-BR". Optional; defaults to English with fallback to whatever track exists.
`video_url`	Yes	YouTube video URL (watch, youtu.be, shorts, embed, live) or a bare 11-character video ID.

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	manual = creator captions, asr = auto-generated.
`title`	No	Video title when known.
`format`	Yes	The output format that was rendered.
`channel`	No	Channel name when known.
`language`	Yes	Language of the DELIVERED track. May differ from the requested language when YouTube refuses on-the-fly translation; the text header says so when it happens.
`video_id`	Yes	The 11-character YouTube video ID.
`characters`	Yes	Length of the rendered transcript text.

TDQS

A4.5/5.0

Behavior5/5

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

Annotations mark the tool read-only and idempotent, and the description adds non-obvious behavior beyond those: instant cached results when available, uncached fetches limited per IP per day, and supported output formats. This meaningfully helps an agent predict cost and behavior.

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 dense sentences with no filler. The core action, input forms, behavioral caveats, and supported formats are all included and front-loaded. Every sentence earns its place.

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?

Given the annotations, complete parameter schema, and output schema, the description covers all essential operational context: what the tool does, how inputs are accepted, caching/rate-limit behavior, and output formats. Nothing needed for correct invocation is missing.

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%; every parameter is already described in the input schema, including URL/ID formats and format semantics. The description mostly restates the supported formats rather than adding new parameter-level meaning, so the baseline 3 applies.

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 states a specific verb and resource: 'Fetch the transcript of a single YouTube video by URL or 11-character video ID.' It is clearly distinct from siblings like get_bulk_download_link and list_videos because it narrows scope to one video's transcript.

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 implies the appropriate use case: retrieving a transcript for a single video, with cache and rate-limit behavior signaling when to expect faster results. It does not explicitly mention alternatives or exclusion conditions, but the single-video scope is clear enough for an agent to route to this tool.

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

All ScriptHaul tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool targets a clearly distinct operation: fetching one transcript, listing videos in a channel/playlist, and generating a bulk download link. There is no meaningful overlap or risk of an agent selecting the wrong tool.

Naming Consistency5/5

Tool names follow a consistent verb_noun pattern: get_transcript, list_videos, and get_bulk_download_link all use a clear action prefix followed by the object. The naming is predictable and easy to reason about.

Tool Count5/5

Three tools is well-scoped for this server's purpose: list to discover videos, get to fetch a single transcript, and bulk link to handle larger downloads. Each tool earns its place without unnecessary bloat.

Completeness5/5

The surface covers the full intended workflow: discovering videos, retrieving individual transcripts in multiple formats, and obtaining a bulk download path. No critical dead ends are apparent for the stated domain.

Resources

Need Help?