Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

youtube_comments

Retrieve top-level YouTube video comments by 11-character video ID and paginate results with continuation tokens for deterministic access.

Instructions

Retrieve top-level video comments. Returns one page of top-level comments for a YouTube video by its 11-character id. Each comment has its id, content, author user_name and channel_id, likes_count, reply_count and published_time. Comments with replies may include their own continuation_token; pass that token to /youtube/comments/{id}/replies. Pass the response-level continuation_token here for deterministic pagination. If omitted, the service discovers an initial cursor or may resume the most recently cached cursor for this video.

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

NameRequiredDescriptionDefault
idYesYouTube video ID (11-character code)
continuation_tokenNoOpaque pagination token returned by a previous request; pass it for deterministic pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.16
    • changedInput schema / properties / continuation_token / description
      Previous value: -"Pagination token returned by a previous request, first page if empty"New value: +"Opaque pagination token returned by a previous request; pass it for deterministic pagination"
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it enumerates the returned fields (id, content, user_name, channel_id, likes_count, reply_count, published_time) and discloses the non-obvious side effect that omitting the token may resume a cached cursor, making results non-deterministic. It does not mention auth requirements, rate limits, sort order, or page size, which is the remaining gap.

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, then progressively adds return shape, reply routing, and pagination semantics. Every sentence carries information, though the final sentence about cursor discovery / cached-cursor resumption is dense and could be split for scanability.

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?

There is no output schema, so the description must describe return values, and it does so field by field, plus it covers pagination and the reply-navigation path. It is missing default ordering and how many comments a page contains, which matter for a paged endpoint, so it is strong but not fully complete.

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 3 is the floor; the description earns above that by explaining what continuation_token actually does (deterministic pagination when passed, cached-cursor fallback when omitted) and by restating the id format in a usage context. That adds semantic value the schema's one-line descriptions do not.

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 ('Retrieve top-level video comments') and explicitly scopes it to top-level comments for a single video identified by an 11-character id. The 'top-level' qualifier plus the pointer to the replies endpoint cleanly separates it from youtube_comment_replies and other youtube_* siblings.

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?

Gives clear operational guidance: use the per-comment continuation_token with the replies path when a comment has replies, and use the response-level token here for deterministic pagination. What's missing is an explicit callout of the sibling tool name (youtube_comment_replies) or a when-not-to-use statement, so it stops short of a 5.

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