YouTube Transcript Downloader

Get Playlist Transcripts

get_playlist_transcripts

Read-only

Get transcripts for the videos in a YouTube playlist (in playlist order) as timestamped markdown, one section per video. Use for working through a course, series, or curated list; for one known video use get_transcript. Read-only; requires an API key. Charges 1 credit per video that returns a transcript, including repeat calls; videos without captions are skipped free. A 10-video call typically costs up to 10 credits, so start with a small limit. Rate limit: 5 requests per 10 seconds.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	YouTube playlist URL (e.g. https://www.youtube.com/playlist?list=PLxxxxxx)
`limit`	No	Number of videos to fetch from the start of the playlist, 1-50 (default 10). Upper bound on the credit charge for this call.

Output Schema

TableJSON Schema

Name	Required	Description
`failed`	Yes	Videos skipped without charge (no captions)
`playlist`	Yes	Playlist title
`succeeded`	Yes	Videos that returned a transcript (each charged 1 credit)
`creditsUsed`	Yes	Credits charged for this call
`totalVideos`	Yes	Videos attempted in this call
`transcripts`	Yes	All transcripts as timestamped markdown, one section per video, divider-separated
`creditsRemaining`	Yes	Account balance after this call

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "creditsRemaining": {
+      "description": "Account balance after this call",
+      "type": "number"
+    },
+    "creditsUsed": {
+      "description": "Credits charged for this call",
+      "type": "number"
+    },
+    "failed": {
+      "description": "Videos skipped without charge (no captions)",
+      "type": "number"
+    },
+    "playlist": {
+      "description": "Playlist title",
+      "type": "string"
+    },
+    "succeeded": {
+      "description": "Videos that returned a transcript (each charged 1 credit)",
+      "type": "number"
+    },
+    "totalVideos": {
+      "description": "Videos attempted in this call",
+      "type": "number"
+    },
+    "transcripts": {
+      "description": "All transcripts as timestamped markdown, one section per video, divider-separated",
+      "type": "string"
+    }
+  },
+  "required": [
+    "playlist",
+    "totalVideos",
+    "succeeded",
+    "failed",
+    "transcripts",
+    "creditsUsed",
+    "creditsRemaining"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 5, 2026

changedInput schema / properties / limit / description

Previous value: -"Number of videos to fetch (default 10, max 50)"New value: +"Number of videos to fetch from the start of the playlist, 1-50 (default 10). Upper bound on the credit charge for this call."

First observedJul 5, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already indicate read-only and non-destructive, but the description adds significant behavioral details: requires an API key, charges 1 credit per transcript retrieved including repeat calls, skips videos without captions, provides a cost estimate, and specifies rate limits. These are valuable beyond the structured annotations.

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 efficiently front-loaded with the main action and output format, followed by usage context, cost, and rate limit. Every sentence contributes unique information with no redundancy or fluff. It is appropriately sized for the tool's complexity.

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

Completeness5/5

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

Given the simple schema (2 params) and existing output schema, the description covers all necessary angles: purpose, ordering, output format, usage contexts, alternative tools, cost behavior, rate limits, and authentication. It is fully complete for an agent to select and invoke confidently.

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% for both 'url' and 'limit', so the baseline is 3. The description adds practical context for the 'limit' parameter by explaining the credit charge per video and advising 'start with a small limit', which meaningfully enhances understanding of cost implications. This exceeds the schema's pure definitional 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 uses a specific verb ('Get transcripts') with a clear resource ('videos in a YouTube playlist') and output format ('timestamped markdown, one section per video'). It explicitly distinguishes itself from sibling tool get_transcript for single videos. This is unambiguous and well-differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use guidance: 'Use for working through a course, series, or curated list' and directly names the alternative for single videos: 'for one known video use get_transcript'. This clearly communicates appropriate contexts and exclusions.

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

All YouTube Transcript Downloader 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?