Skip to main content
Glama
YouTube MCP Server

YouTube MCP Server

Get replies to a comment

get_comment_replies
Read-onlyIdempotent

Retrieve all replies in a YouTube comment thread, including paginated results beyond the initial comment list, by supplying the thread comment ID.

Instructions

All replies to one comment thread, for threads with more replies than list_comments includes.

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": {
      "comment_id": "<comment_id>"
    },
    "name": "get_comment_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
comment_idYesthread_id of a comment from list_comments.
page_tokenNonext_page_token from a previous call, for the next page.
max_resultsNoReplies per page, 1-100.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only the relationship to list_comments; it says nothing about reply ordering, whether pagination must be iterated until exhausted, or rate/visibility limits. With annotations and an output schema present, this is adequate but thin.

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?

A single short sentence with no filler, and the scope is front-loaded ahead of the sibling reference. It is elliptical rather than a full sentence, but nothing extraneous is present.

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 three-parameter read tool with full schema documentation, an output schema, and complete safety annotations, the description's main remaining job is routing, which it does. A note on iterating pagination would make it fully complete, but the page_token description already implies the loop.

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%, with comment_id, page_token, and max_results all documented in detail (including the 1-100 bound and the next_page_token contract). The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 resource and scope: 'All replies to one comment thread.' The verb is implicit ('get replies') rather than explicit, but the object is unambiguous. It also ties itself to the sibling list_comments, so an agent can distinguish the two without opening the schemas.

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?

Provides a clear selection condition: use this for threads with more replies than list_comments includes. That names the alternative and the circumstance that routes to this tool. No explicit when-not or prerequisite guidance (e.g., auth requirement) is given, which keeps it below a 5.

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