Skip to main content
Glama
fetchtranscript-mcp

fetchtranscript-mcp

Official

get_comments

Fetches top comments from a YouTube video by video ID, with an adjustable limit, so you can analyze audience reactions and discussion.

Instructions

Get top comments on a YouTube video.

Args: video_id: YouTube video ID (11 characters) limit: Number of comments to fetch (default 20, max 500)

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_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
video_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description bears the full burden and does disclose the default (20) and hard cap (500) on results, which is useful behavioral context. However, it says nothing about authentication requirements, rate limits, pagination, whether replies are included, or what 'top' ordering actually means, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and the args list is compact with no filler. The parameter block partially restates the schema, but the added format and bounds justify its presence.

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 simple two-parameter read tool with an output schema already documenting return values, the description covers purpose and both parameters adequately. The main missing piece is ordering/pagination behavior for results beyond 500, which is a minor gap given the tool's simplicity.

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 description coverage is 0%, so the description must compensate, and it largely does: it specifies video_id is an 11-character YouTube ID and documents limit's default and maximum. It doesn't state limit's unit semantics beyond 'number of comments' or what happens if a value exceeds 500, but the core meaning is added.

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 gives a specific verb and resource ('Get top comments on a YouTube video'), which is clearly distinguishable from siblings like get_transcript, get_chapters, and get_video_metadata. It doesn't explicitly name a sibling, but the resource noun alone 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?

Usage is only implied by the purpose statement; there is no explicit guidance on when to call this versus get_video_metadata or get_transcript, and no prerequisites are mentioned. An agent can infer the use case, but nothing is stated about context or exclusions.

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