yt-consolidado

youtube_get_transcript

Retrieves a YouTube video's transcript from public timedtext data, with optional language selection and timestamps, so you can read or process spoken content without manual transcription.

Instructions

Video transcript — port of tube-bridge youtube_get_transcript.

Layer: public timedtext. Quota: 0 units, no key.

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

Name	Required	Description	Default
`url`	Yes
`lang`	No
`with_timestamps`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

C2.2/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose cost/access behavior ("Quota: 0 units, no key", "public timedtext"), which is genuinely useful, but says nothing about failure modes (no captions, region blocks), whether transcripts are auto-generated, or what happens when lang is unavailable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and the resource is stated up front, but a meaningful share of the text is spent on internal provenance ("port of tube-bridge", "Layer: public timedtext") that gives an agent little operational value.

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?

An output schema exists, so return shape need not be explained, but for a 3-parameter tool with zero schema documentation and no annotations the description is far too thin. Key calling information — accepted url forms, language fallback behavior, and the timestamps flag — is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 3 parameters, and the description compensates for none of them. It does not explain the url format expected, what lang values are accepted or how null resolves, or what with_timestamps changes in the output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase "Video transcript" identifies the resource being returned, and the sibling tools (youtube_get_video_info, youtube_get_channel_videos) address different resources, so the agent can roughly place it. However, there is no verb and no explicit differentiation — the sentence is a label rather than a statement of what the tool does.

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?

The description gives no when-to-use guidance and names no alternative. An agent cannot tell from this text whether to reach for transcripts versus youtube_get_video_info, and nothing indicates prerequisites such as the video needing captions available.

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

Deploy Server