Crawlora MCP

youtube_comments

Read-only

Fetch top-level comment items for one YouTube video. Use the response continuation_token for the next top-level page; each comment may also carry its own continuation_token for youtube_comment_replies. Use youtube_video for video metadata.

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": {
      "id": "<id>"
    },
    "name": "youtube_comments"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	YouTube video, playlist, or channel id/handle/URL.
`continuation_token`	No	Pagination token from a previous response.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description's real contribution is pagination behavior — that the top-level page token comes from the response and that each comment may carry its own token for replies. It omits ordering, result count, and rate-limit behavior, so it adds context but not a rich behavioral picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each carrying distinct information (purpose, pagination mechanism, sibling routing), with the core purpose front-loaded and zero 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?

An output schema exists, so return values need not be described. The pagination contract and sibling routing are covered; the only remaining gap is how the id parameter resolves non-video inputs, which the description implicitly narrows to videos without addressing the schema's broader wording.

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 the baseline is 3; the description goes beyond it by clarifying that continuation_token comes from a previous response and that there are two distinct token kinds (top-level page vs per-comment reply). It does not clarify the id parameter's video-vs-playlist-vs-channel ambiguity.

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?

States a specific verb and resource ("Fetch top-level comment items for one YouTube video") and explicitly scopes it to top-level comments, distinguishing it from youtube_comment_replies and youtube_video by name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternatives and the conditions that select them: youtube_comment_replies for per-comment threads and youtube_video for video metadata. An agent can route correctly without opening another schema.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?