A
licenseA
qualityB
maintenanceExtract YouTube transcripts for AI agents, RAG pipelines, and LLM workflows. Supports any YouTube URL. Returns clean text or timestamped segments. No API keys required.
1
4
MIT
ScriptHaul
Server Details
Free YouTube transcript fetcher: clean text, timestamped, SRT, VTT, Markdown, or JSON. No API key.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Available Tools
3 toolsget_bulk_download_linkGet bulk download linkARead-onlyIdempotentInspect
For a YouTube channel or playlist URL, returns a prefilled scripthaul.com link where the user can download every transcript as a ZIP for free. Bulk jobs cannot run over MCP; they need the website.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | YouTube channel or playlist URL (also accepts @handles). |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| url | Yes | Prefilled scripthaul.com link that starts the bulk download. |
| type | Yes | What the input resolved to. |
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds meaningful behavioral context: the tool does not run the bulk job itself, it only returns a prefilled external link, and the download is free. This goes beyond the annotation metadata and clarifies the tool's side-effect-free nature.
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?
The description is two sentences with no filler. The key output is front-loaded, and the second sentence adds the essential MCP limitation. 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?
For a single-parameter, read-only tool with an output schema and annotations, this description is complete. It covers input (channel/playlist URL), output (prefilled download link), cost (free), and the key constraint (bulk jobs need the website). Nothing essential 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 description coverage is 100%, and the single 'url' parameter is already clearly described in the schema as 'YouTube channel or playlist URL (also accepts @handles).' The description restates the accepted URL types but does not add new parameter details beyond the schema, so the baseline of 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 ('returns') and a specific resource ('prefilled scripthaul.com link') for a well-defined input ('YouTube channel or playlist URL'). It clearly differentiates this bulk-download tool from the sibling tools get_transcript and list_videos by focusing on ZIP downloads of every 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 explicitly says bulk jobs cannot run over MCP and require the website, which tells the agent when to invoke this tool and what limitation applies. It does not explicitly name the alternative for single-transcript cases, but the context and sibling list make the distinction clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_transcriptGet YouTube transcriptARead-onlyIdempotentInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| 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
ParametersJSON 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.
list_videosList videos in a channel or playlistARead-onlyIdempotentInspect
List the videos of a YouTube channel or playlist: date, video ID, and title for each. Use this to answer questions about a channel — pick the relevant videos by title, then call get_transcript for each one. Listings are cached for a few hours; a fresh enumeration counts against the same daily allowance as uncached fetches.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | YouTube channel or playlist URL (also accepts @handles). | |
| limit | No | Maximum videos to list, newest first for channels. Default 100, maximum 200. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
| type | Yes | |
| shown | Yes | How many are included below (bounded by limit). |
| title | No | Channel or playlist title when known. |
| videos | Yes | |
| truncated | No | True when the source has more videos than one enumeration returns (500). |
| video_count | Yes | Total videos in the listing snapshot. |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds meaningful behavioral context beyond the annotations: 'Listings are cached for a few hours; a fresh enumeration counts against the same daily allowance as uncached fetches.' This introduces caching and quota-cost trade-offs that the agent would not otherwise know from readOnlyHint, openWorldHint, or idempotentHint alone. It does not contradict any annotation.
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?
The description is two sentences: the first states the core function and output, the second gives usage guidance and behavioral caveats. There is no filler, every sentence earns its place, and the most important information is front-loaded.
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?
For a two-parameter read-only tool with an output schema and annotations covering safety and open-world semantics, the description covers the essential context: what it lists, how to use it with a sibling, and the caching/rate-limit caveat. Nothing needed to call it correctly 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 description coverage is 100%, so the baseline is 3. The description does not add meaning to the url or limit parameters beyond what the schema already provides; it focuses instead on output content and workflow. This is acceptable because the schema already documents both parameters fully, but the description contributes no additional parameter-level insight.
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 ('List'), a precise resource ('the videos of a YouTube channel or playlist'), and the exact fields returned ('date, video ID, and title'). It also distinguishes itself from the get_transcript sibling by explicitly routing to it as a next step, so an agent can tell immediately what this tool does and what it does not do.
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?
The description gives explicit usage context: 'Use this to answer questions about a channel — pick the relevant videos by title, then call get_transcript for each one.' This clearly tells an agent when to use the tool and how it fits into a larger workflow, directly naming the sibling tool that should follow. It implicitly excludes get_transcript as a substitute for listing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
3 tool updates
- First observed
get_bulk_download_link - First observed
get_transcript - First observed
list_videos
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Fetch the full transcript of any YouTube video as clean text. No API key, no signup.
Clean YouTube transcripts for agents: single videos, channels, playlists, plus AI caption cleanup.
Fetch transcripts, subtitles, chapters, metadata and frames from YouTube and 10+ video platforms
YouTube transcripts, search, channel/playlist listings and upload tracking for AI agents. No signup.
Related MCP Servers
- AlicenseAqualityDmaintenanceExtracts clean text transcripts from YouTube videos using their subtitles and returns them as plain text.122MIT
- AlicenseAqualityFmaintenanceRetrieves transcripts from YouTube videos with support for multiple languages, timestamp control, and language detection. Enables video content analysis, summarization, and quote extraction without manually downloading or watching videos.212315MIT
- AlicenseNot gradedqualityCmaintenanceA powerful text extraction service that converts YouTube video content into clean, timestampless transcripts for content analysis, research, and processing workflows.3Apache 2.0
Try in Browser
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.