Skip to main content
Glama

YouTube comments of a video

youtube_comments
Read-onlyIdempotent

List a YouTube video's comments, top comments first or newest first, about 20 per page, each with author, text, likes, reply count, age, and pinned and creator-heart flags; the first page also gives the exact comment count. A video with comments turned off returns an empty page. First page: give url (and sort). Next pages: give only cursor until next_cursor is null.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA YouTube video link (watch, youtu.be, Shorts, live or embed link) or its 11-character id (_T8cn2J13-4).
sortNoTop comments first, or newest first.top
cursorNoThe next_cursor of the previous answer, exactly as returned, for the next page. Leave it out for the first page; with it, nothing else is needed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare it a safe, idempotent, open-world read; the description adds genuinely new behavior — page size (~20), exact comment count on the first page only, the returned fields, and the empty-page result when comments are off.

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?

Front-loads the resource and result shape, then the pagination contract in two short sentences. The opening sentence is long and heavily punctuated, but nearly every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description fully compensates by naming the returned fields, the page size, and the terminal condition for pagination. Nothing an agent needs to call or continue calls is missing.

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 coverage is 100% so the baseline is 3, but the description adds real meaning beyond it by specifying the pagination contract (url+sort on page one, cursor alone afterwards) and the effect of sort on ordering.

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

Purpose5/5

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

Opens with a specific verb+resource ('List a YouTube video's comments') and immediately scopes the operation with ordering options, so it is unmistakably distinct from siblings like youtube_video or youtube_transcript.

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?

Gives an explicit calling protocol: first page passes url (and sort), later pages pass only cursor until next_cursor is null, plus the edge case that disabled comments yield an empty page. It does not route the agent away to alternatives (e.g. youtube_video for metadata), so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources