Skip to main content
Glama
Sign In
OmniContext

OmniContext

by h4sht
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get YouTube transcript

youtube_get_transcript

Fetch the transcript or captions of a YouTube video as plain text by providing its URL or ID. No login required.

Instructions

Fetches the transcript/captions of a YouTube video as plain text. No login or setup required — just paste a video link or ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "youtube_get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA YouTube video URL (e.g. https://youtube.com/watch?v=..., https://youtu.be/..., or a Shorts link) or an 11-character video ID.
langNoOptional ISO language code for the transcript (e.g. 'en', 'es'). Defaults to the video's default caption track.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that no login or setup is required, which is positive. However, it does not mention potential rate limits, what happens if the transcript is unavailable, or any error conditions. For a simple read tool, this is adequate but lacks depth.

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 zero wasted words. The first sentence states the core purpose, the second adds context about authentication and input convenience. Every sentence serves a purpose.

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?

The tool is simple with 2 parameters and no output schema. The description covers the essential input and authentication context. It omits details about return format (raw text vs segmented) and failure cases, but for a transcript fetch tool, these are common knowledge. Slightly incomplete but mostly sufficient.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by clarifying the 'url' parameter accepts various YouTube URL formats or a video ID, which goes beyond the schema's generic description. For 'lang', it merely repeats the schema's default behavior, so no extra credit there.

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 fetches transcript/captions of a YouTube video as plain text. It uses a specific verb ('Fetches') and resource, distinct from sibling 'youtube_save_transcript' which likely saves. The 'No login or setup required' note further clarifies scope.

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 clear input guidance: 'just paste a video link or ID.' It explains accepted formats (full URL, Shorts link, or video ID). However, it does not explicitly mention when not to use it (e.g., if video has no captions) or compare to alternatives like youtube_save_transcript.

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

Deploy Server

Other Tools