Skip to main content
Glama
youtube-transcript-leads-mcp

youtube-transcript-leads-mcp

by willowswt

extract_youtube_transcript_and_rag

Read-onlyIdempotent

Extracts multi-language YouTube transcripts, timestamped chapters, and metadata, then converts them into token-bounded RAG chunks with timestamp deep-links for retrieval and analysis.

Instructions

Extract full multi-language YouTube transcripts, timestamped chapters, metadata, and token-bounded RAG chunks with deep-links from video URLs or IDs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_youtube_transcript_and_rag"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoUrlNoSingle YouTube video URL, Short URL, or 11-character Video ID.
videoUrlsNoList of YouTube video URLs or IDs for batch extraction.
chunkSizeWordsNoWords per semantic RAG chunk with timestamp deep-links.
targetLanguageNoPreferred ISO transcript language code (e.g. 'en', 'es', 'fr').en
includeMetadataNoInclude title, channel metadata, views, and chapters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered externally. The description adds useful output-content context such as multi-language transcripts, timestamped chapters, and token-bounded RAG chunks with deep-links, but does not disclose failure behavior, language fallback, or rate limits.

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 definition is a single front-loaded sentence with no wasted wording. Each phrase contributes to identifying the extraction scope and output artifacts.

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?

For a moderately complex read-only extraction tool with five optional parameters and no output schema, the description sufficiently names the main outputs: transcripts, chapters, metadata, and RAG chunks. It could be stronger by clarifying batch behavior or transcript fallback, but it covers the essential purpose and result shape.

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 input schema already explains videoUrl, videoUrls, chunkSizeWords, targetLanguage, and includeMetadata. The description adds only high-level context like multi-language support and token-bounded chunks, without adding syntax or constraints beyond the schema.

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 uses a specific verb, 'Extract', with a precise resource set: YouTube transcripts, chapters, metadata, and RAG chunks. It clearly distinguishes this from the sibling channel-email tool by focusing on video content extraction from URLs or IDs.

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

Usage Guidelines3/5

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

The description implies usage by mentioning video URLs or IDs, but it does not explicitly state when to use this tool versus alternatives, nor does it give exclusions such as unsupported videos or batch limits. Usage context is inferable but not fully guided.

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