Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

List comments

list_comments
Read-onlyIdempotent

Retrieves public comment threads from a video or channel's videos, including text, author, likes, date, reply counts, and whether the owner replied; supports pagination.

Instructions

Public comment threads on a video or on all of a channel's videos: text, author, likes, date, reply count, first replies.

owner_replied tells whether the channel answered in the included replies, which helps find unanswered questions. Paginated via next_page_token; 1 quota unit per page. Held-for-review comments are not visible.

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": "list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNotime (newest first) or relevance (relevance only together with video_id).time
searchNoOnly threads containing this text.
channelNoChannel ID (UC...) or handle (@name). Omit for your own channel (OAuth) or the configured default.
video_idNoComments on this video. Omit for comments on all of the channel's videos.
page_tokenNonext_page_token from a previous call, for the next page.
max_resultsNoThreads per page, 1-100.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare this a safe, idempotent, non-destructive read, so the description correctly spends its budget elsewhere. It discloses pagination via next_page_token, a concrete cost of 1 quota unit per page, and the important exclusion that held-for-review comments are not visible — all facts an agent cannot obtain from the structured fields.

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?

Four short, front-loaded segments: what is returned, the owner_replied interpretation, pagination and cost, then the visibility caveat. Nothing is wasted, though the field list and the owner_replied sentence read as fragments rather than a flowing explanation.

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 annotations covering safety, a full output schema covering return shape, and 100% schema coverage on all six optional parameters, the description only needs to add pagination, cost, and visibility caveats — and it does exactly that. Nothing an agent needs to call this correctly is missing.

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 100%, so every parameter including the order/video_id interplay and channel defaulting is already documented in the schema. The description only echoes next_page_token in passing and adds no syntax or format detail beyond that, making the baseline 3 appropriate.

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 opening clause names a specific resource and scope: public comment threads on a video or across a channel's videos, plus the fields returned (text, author, likes, date, reply count, first replies). The mention of included 'first replies' hints at a boundary with the replies-specific sibling, but no sibling is named outright, so an agent must infer that get_comment_replies covers deeper reply traversal.

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 description gives a use case — 'owner_replied ... helps find unanswered questions' — which implies a screening workflow, and it notes the visibility limit for held-for-review comments. It stops short of stating when to prefer this tool over get_comment_replies or search_videos, so guidance is implied rather than explicit.

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