Skip to main content
Glama

List comments on a YouTube video

list_youtube_comments
Read-onlyIdempotent

Read the comments on a YouTube video: each top-level comment with its author, text, likes, date, reply count and up to 5 replies, and by_you on comments the connected channel wrote. YouTube is in platform review: this only works for an account with a YouTube channel connected (list_accounts). Pass next_page_token back as page_token for more.

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": "<video>"
    },
    "name": "list_youtube_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoOptional. "time" (default, newest first) or "relevance".
videoYesThe video id or a link to the video.
searchNoOptional. Only comments containing this text.
accountNoOptional. Which connected YouTube channel to read as (handle or id from list_accounts). Default: the default channel.
page_tokenNoOptional. next_page_token from the previous call.
max_resultsNoOptional. Comments per page, 1 to 100 (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: the platform-review access restriction and the reply-depth cap (up to 5 replies). It does not mention rate limits, error behavior when no channel is connected, or whether by_you depends on the account parameter.

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-loaded with the core action and return shape, then prerequisites, then pagination — a logical order. It is dense (one long sentence plus two short ones) and the by_you clause sits awkwardly mid-list, but no sentence is filler.

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?

With no output schema, the description carries the return-shape burden and does so by listing the comment fields and reply truncation. Prerequisites and pagination are covered; what's missing is failure behavior when no YouTube channel exists and whether search applies to replies.

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 all six parameters are already documented. The description still adds a useful round-trip detail the schema lacks: that the response's next_page_token should be fed back as page_token, and it ties the account parameter to the channel-connection prerequisite.

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 and resource ("Read the comments on a YouTube video") and immediately enumerates the returned fields — author, text, likes, date, reply count, up to 5 replies, and a by_you flag. This distinguishes it from the write-side sibling reply_to_youtube_comment without needing to open either schema.

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?

States a hard prerequisite ("only works for an account with a YouTube channel connected") and routes the agent to list_accounts to establish that, plus instructs how to continue paging. It never explicitly contrasts read vs. reply use cases, so exclusions are absent.

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