Skip to main content
Glama
thenavidm

YouTube MCP

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get several transcripts

get_transcripts
Read-onlyIdempotent

Fetch transcripts from up to 20 YouTube videos in one call, including Shorts and live URLs, to compare openings or build a corpus. Missing captions are reported without failing the batch.

Instructions

Fetch transcripts for up to 20 videos in one call. A video with no captions is reported in place rather than failing the batch. Use it to compare how a set of videos open, or to build a corpus before analyzing it.

Input Schema

NameRequiredDescriptionDefault
videosYesUp to 20 video ids or URLs.
languageNo
max_chars_eachNoTruncate each transcript to this many characters. Useful when you only need the openings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.2
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds real value beyond that by disclosing partial-failure semantics: a video without captions is reported in place rather than failing the batch, which materially affects how the agent should handle results.

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, zero filler, with the core capability and the 20-item bound front-loaded before the edge-case and use-case notes. Every sentence carries distinct information.

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 read-only batch tool with full annotation coverage and no output schema, the description covers capability, limits, failure handling, and motivation adequately. The only gap is the unexplained 'language' parameter, which no structured field clarifies either.

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 coverage is 67% and the schema already documents the URL/id formats and the max_chars_each truncation purpose. The description reinforces the 20-item cap and hints at the truncation use case ('openings'), but the 'language' parameter is undocumented in both schema and description, so it adds only marginal value.

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 ('Fetch transcripts') plus a precise scope ('up to 20 videos in one call'), which implicitly separates it from the singular sibling get_transcript. It stops short of naming that sibling, so an agent must infer the batch-vs-single split rather than being told it.

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?

Two concrete use cases are given ('compare how a set of videos open', 'build a corpus before analyzing it'), which tell the agent when this tool is the right choice. There is no explicit exclusion or pointer to get_transcript for the single-video case, so it falls just short of the top band.

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