Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_comment_replies

Fetch replies to a single YouTube comment and paginate results by passing the comment's continuation token to retrieve each additional page.

Instructions

Retrieve replies to one YouTube comment. Returns one page of replies using the opaque continuation_token on a comment from /youtube/comments/{id}. The path id is the 11-character video ID that provides the YouTube watch-page context. Pass the response-level continuation_token to fetch another replies page.

Input Schema

NameRequiredDescriptionDefault
idYesYouTube video ID (11-character code)
continuation_tokenYesOpaque per-comment reply token from a comment object

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the paginated, one-page-at-a-time behavior, that the token is opaque, and that `id` supplies watch-page context rather than selecting the comment. It says nothing about auth requirements, rate limits, or what happens on an exhausted/expired token.

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 tight sentences, front-loaded with the purpose before the mechanics. The final sentence slightly restates the pagination point already implied by 'one page of replies using the opaque continuation_token'.

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 two-parameter, read-only retrieval tool with a fully described schema and no output schema, the description covers what an agent needs to call it correctly: inputs, their provenance, and the paging loop. Return-shape detail is the only thing left implicit, which is partly covered by 'Returns one page of replies'.

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 both parameters are already documented, establishing the baseline of 3. The description only adds the provenance detail that the token is 'response-level' and comes from a comment object — marginal value over the schema's 'Opaque per-comment reply token from a comment object'.

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 and resource ('Retrieve replies to one YouTube comment') with an explicit cardinality constraint that separates it from listing comments on a video. It does not name `youtube_comments` as the sibling to use for top-level comments, so differentiation is by implication rather than explicit routing.

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?

Explains the prerequisite chain clearly: get a comment from `/youtube/comments/{id}`, take its `continuation_token`, and call this tool; then pass the response-level token to page further. No explicit when-not-to-use or alternative is given, but the workflow context is unambiguous.

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

Deploy Server

Other Tools