Skip to main content
Glama
Sign In
jkawamoto

YouTube Transcript MCP Server

by jkawamoto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_timed_transcript

Retrieves the timed transcript of a YouTube video by URL, supporting language selection and pagination. Use it to extract timestamped captions for processing or analysis.

Instructions

Retrieves the transcript of a YouTube video with timestamps.

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL of the YouTube video
langNoThe preferred language for the transcripten
next_cursorNoCursor to retrieve the next page of the transcript

Output Schema

NameRequiredDescriptionDefault
titleYesTitle of the video
snippetsYesTranscript snippets of the video
next_cursorNoCursor to retrieve the next page of the transcript

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.3
    • changedInput schema / properties / next_cursor / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedOutput schema / properties / next_cursor / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Addedv1.0.0

TDQS

B3.3/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 behavioral disclosure burden. It states the basic retrieval behavior but does not mention pagination behavior despite the next_cursor parameter, language fallback behavior, error cases, or rate limits.

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 front-loaded sentence with no wasted words. It immediately communicates the core capability.

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?

The tool has an output schema and full parameter descriptions, which reduces the description's burden. However, the description does not address pagination, language preference behavior, or sibling differentiation, leaving some contextual gaps.

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 description coverage is 100%, so the schema already documents url, lang, and next_cursor. The description adds no parameter meaning beyond the schema, which is acceptable but not additive.

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

Purpose4/5

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

The description states a specific verb and resource: retrieves the transcript of a YouTube video, with timestamps. This is clear, but it does not explicitly distinguish itself from the sibling get_transcript beyond the implied timestamp feature.

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

Usage Guidelines3/5

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

The phrase 'with timestamps' implies when this tool is preferable, but the description gives no explicit guidance about when to use it instead of get_transcript or how it relates to get_available_languages.

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