yt-summarizer

get_transcript

Fetch the transcript of a YouTube video by supplying its ID or URL, making it available for summarization and analysis.

Instructions

Fetch the transcript of a YouTube video.

Args: video_id: A YouTube video ID or full video URL (watch, youtu.be, shorts, etc.)

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": {
      "video_id": "<video_id>"
    },
    "name": "get_transcript"
  }
}

Input Schema

Name	Required	Description	Default
`video_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavior. It does not mention what the transcript contains (e.g., auto-generated vs manual), whether authentication is required, any rate limits, or what happens if the video ID is invalid. The description adds no behavioral context beyond the basic action.

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 extremely concise, with two short sentences that deliver the core purpose and parameter details without filler. It is front-loaded with the main action.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, output schema exists), the description covers the essential info about accepted input formats. However, it lacks guidance on when to use the tool and does not describe the transcript output structure or any error cases, leaving some gaps for a production tool.

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?

The schema provides only 'video_id' as a string, but the description adds crucial clarity by specifying accepted formats: 'A YouTube video ID or full video URL (watch, youtu.be, shorts, etc.)'. This directly compensates for the 0% schema description coverage.

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 'Fetch the transcript of a YouTube video', using a specific verb and resource. It is easily distinguished from the sibling tool create_notion_page, which serves a completely different purpose.

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 guidance is provided on when to use this tool vs alternatives. There are no mentions of prerequisites, limitations, or scenarios where another tool might be preferred. The description only gives argument instructions.

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

Deploy Server