Skip to main content
Glama
Sign In
yt-media-info-mcp

yt-media-info-mcp

by bartivs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_transcript

Retrieve subtitles or transcript text from any media URL. Optionally include timestamp segments and specify language.

Instructions

Fetch subtitles or transcript text for a media URL, optionally with timestamp segments

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": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesMedia URL to fetch transcript from
languageNoPreferred subtitle language code (e.g. "en", "es")en
passwordNoPassword for site authentication
usernameNoUsername for site authentication
timestampsNoInclude timestamp segments in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions optional timestamps but does not describe output format, error handling, rate limits, authentication requirements (despite username/password params), or any side effects. The behavior is only superficially described.

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 a single sentence with no wasted words. It is front-loaded with the core action ('Fetch subtitles or transcript text') and mentions the key optional feature. Every word serves a purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of annotations and output schema, and the presence of authentication-related parameters (username, password), the description should provide more context on return values, error scenarios, and authentication flow. As is, it leaves significant gaps for a non-trivial tool with 5 parameters.

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 the schema already documents all parameters adequately. The description adds 'optionally with timestamp segments' which corresponds to the timestamps parameter but does not enhance schema information. Baseline score of 3 is appropriate.

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?

Description clearly states the tool fetches subtitles or transcript text from a media URL with optional timestamps. It uses a specific verb ('Fetch') and resource ('subtitles or transcript text'), and distinguishes itself from siblings like 'extract_info' (metadata extraction) and 'search_media' (search).

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention when not to use it, nor does it reference sibling tools or provide context for preferred usage scenarios. The agent must infer use from the description alone.

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