Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_list_caption_tracks

Read-only

Lists caption tracks for an owned creator video using its YouTube video ID, helping you identify available captions before managing or editing them.

Instructions

List caption tracks for an owned creator video.

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": {
      "videoId": "<videoId>"
    },
    "name": "youtube_list_caption_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesYouTube video ID (11 characters), e.g. dQw4w9WgXcQ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / videoId / description
      Added value: +"YouTube video ID (11 characters), e.g. dQw4w9WgXcQ."
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The readOnlyHint annotation already declares this is a safe read. The description adds one useful behavioral fact — the video must be an owned creator video, implying an auth/ownership precondition. It says nothing about what tracks are returned (language, kind, availability) or failure modes for non-owned videos.

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?

One short sentence, front-loaded with the verb and resource, with no redundant or filler text.

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?

For a one-parameter read-only list tool with full schema coverage this is roughly adequate, but with no output schema the description could have said what a caption track record contains (language code, name, kind) and whether the list is paginated. As-is an agent knows how to call it but not what it will get back.

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 100% and the single videoId parameter is fully documented in the schema, so the baseline is 3. The description only reinforces that the videoId must reference an owned creator video, adding minimal semantics beyond the schema.

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?

States a specific verb and resource ('List caption tracks') scoped to 'an owned creator video', which distinguishes it from caption-mutating siblings like youtube_download_caption or youtube_upload_caption. It doesn't name an alternative explicitly, but the read-only listing purpose is unambiguous.

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 'owned creator video' implies this applies to videos the authenticated user owns, but there is no explicit when-to-use vs. when-not guidance or named alternative (e.g., use download_caption to fetch track content). Usage is inferable but not stated.

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