Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

get_chapters

Retrieve the chapter list for a YouTube video using its video ID to navigate key sections and summarize content without scanning the full transcript.

Instructions

Get chapter list for a YouTube video.

Args: video_id: YouTube video ID (11 characters)

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": {
      "video_id": "<video_id>"
    },
    "name": "get_chapters"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of disclosure. 'Get' implies a read operation, but nothing is said about permission requirements, rate limits, or what happens for videos that have no chapters (empty list versus error), which is the most likely failure mode for this tool.

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?

Two short lines; the purpose is front-loaded in the first sentence and the Args block contributes a non-obvious format constraint rather than restating the schema. Nothing is superfluous.

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 is simple with one required parameter and an output schema, so return-value documentation is not needed. The gaps are the no-chapters behavior and the lack of differentiation from related read tools, which matter for correct routing.

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 0%, so the description must compensate, and it partially does by specifying that video_id is an 11-character YouTube video ID. It does not say where to obtain that ID or what happens when a malformed or non-existent ID is supplied.

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 ('Get chapter list for a YouTube video'), which is unambiguous about what is returned. It does not differentiate itself from adjacent siblings such as get_transcript or get_video_metadata, so an agent must infer which of the two to pick when a user asks about video structure.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no exclusions, and no mention of alternatives like get_transcript. The only guidance is implicit in the name and first sentence, leaving the agent to reason about whether chapters or the full transcript is wanted.

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