Skip to main content
Glama

youtube_list_comments

Read-onlyIdempotent

List comment threads on a YouTube video. Pass video_id (e.g. 'dQw4w9WgXcQ') or channel_ref ('youtube:video:'). Returns top-level comments with inline replies.

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

Input Schema

NameRequiredDescriptionDefault
video_idYesYouTube videoId — bare 11-char form OR full 'youtube:video:<id>'.
account_idNoWhich connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.
page_tokenNoPagination cursor from a previous call's `next_page_token`.
max_resultsNoPage size, 1-100. Default 25.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Which connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description adds one useful behavioral fact — that top-level comments come back with inline replies — but says nothing about quota costs, ordering, or pagination behavior beyond what the schema already documents.

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?

Three short sentences, front-loaded with the purpose and followed by invocation and return shape — efficient overall. The parenthetical about channel_ref is the one piece of wording that does not earn its place, since no such parameter exists.

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 annotations carrying the safety profile and a fully described schema, the description only needs to add the return shape, which it does by noting top-level comments plus inline replies. The account_id refusal behavior and multi-channel disambiguation are left entirely to the schema.

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 coverage is 100%, so all five parameters are already documented in the schema, making 3 the baseline. The description's example video_id adds a little concrete form, but its mention of a 'channel_ref' parameter that does not exist in the schema introduces confusion rather than meaning.

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?

States a specific verb ('List') and resource ('comment threads on a YouTube video'), which cleanly separates it from the delete/moderate/post_comment_reply siblings. It stops short of naming those siblings explicitly, so an agent must infer the boundary from the resource alone.

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 implied by the resource ('list comment threads on a video'), and the read-only nature is reinforced by the annotations. There is no explicit statement of when to prefer this over youtube_video_query or the moderation tools, nor any prerequisite guidance beyond parameter passing.

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.