TranscriptYT

Get YouTube transcript

get_transcript

Read-only

Fetch the transcript of a public YouTube video. Accepts a full URL or an 11-character video ID. Defaults to Markdown (title + text), which is the most compact format for reading or summarizing. Use json for timestamped segments, srt/vtt for subtitle files. Costs 1 credit on success; videos without captions are AI-transcribed at 1 credit per started minute (paid plans and credit packs; Free reads captions only).

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

Name	Required	Description	Default
`url`	Yes	YouTube URL or video ID
`mode`	No	auto: captions, AI-transcribed audio if there are none. captions: never AI. ai: always transcribe the audio (1 credit per started minute). AI needs a paid plan or credit pack	auto
`format`	No	Output format	md
`search`	No	Only return lines containing this text
`end_time`	No	Only return the part before this second
`language`	No	Preferred caption language (BCP-47, e.g. en, es, pt-BR)
`start_time`	No	Only return the part from this second on
`timestamps`	No	Prefix lines with timestamps (text/md)
`translate_to`	No	Translate the transcript into this language
`original_language`	No	Prefer the spoken language's captions over English

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 10, 2026

changedInput schema / properties / mode / description

Previous value: -"auto: captions, AI-transcribed audio if there are none. captions: never AI. ai: always transcribe the audio (1 credit per started minute)"New value: +"auto: captions, AI-transcribed audio if there are none. captions: never AI. ai: always transcribe the audio (1 credit per started minute). AI needs a paid plan or credit pack"

First observedNov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, and the description adds substantial behavior the annotations cannot: a 1-credit cost on success, a per-started-minute charge for AI transcription, and the Free-tier limitation of captions-only. It does not cover failure/refund behavior or rate limits, which keeps it below a 5.

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?

Three sentences, front-loaded with purpose, then input forms, then format guidance, then cost. No filler and nothing repeated from the schema verbatim.

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 10-parameter tool with no output schema, the description is unusually complete: it explains the default output shape, the mode/format tradeoffs, and the billing model. Gaps remain on error conditions and on the exact shape of json/srt/vtt output, which an agent must infer.

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 the baseline is 3; the description earns above that by explaining what the md default actually contains (title + text) and by characterizing formats by purpose (json = timestamped segments, srt/vtt = subtitle files). That adds intent the terse schema labels do not.

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?

Opens with a specific verb+resource ("Fetch the transcript of a public YouTube video") and names the accepted input forms (full URL or 11-character video ID). It is clearly distinguishable from siblings like summarize_video or search_youtube, which do different work.

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?

Gives real selection guidance: default to Markdown for reading/summarizing, use json for timestamped segments, srt/vtt for subtitle files. It also explains the plan gating that determines whether AI transcription is available. It stops short of explicitly routing the agent away from siblings (e.g. when to prefer summarize_video).

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

All TranscriptYT tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?