Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

youtube_comments

Fetch YouTube video comments (top-level and replies) using an 11-character video ID. Returns one page; pass continuation_token for next pages.

Instructions

Retrieve video comments (top-level & replies). Returns one page of 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. Pass the previous response's continuation_token to get the next page; leave it empty for the first.

Input Schema

NameRequiredDescriptionDefault
idYesYouTube video ID (11-character code)
continuation_tokenNoPagination token returned by a previous request, first page if empty

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 reasonably well: it discloses the paginated nature ('returns one page'), the continuation_token loop behavior, and the exact fields returned per comment (id, content, user_name, channel_id, likes_count, reply_count, published_time). It does not mention ordering, per-page limits, or auth needs, so it falls short of the richest disclosure but is well beyond minimal.

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 sentences, front-loaded with the purpose and pagination mechanics before the field enumeration. The field list is somewhat dense but earns its place since there is no output schema, so it is only mildly overlong.

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 2-param read tool with no annotations and no output schema, the description compensates well by enumerating the returned comment fields and explaining pagination. The remaining gaps (ordering, page size, auth) are minor for this kind of public read endpoint.

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%, so the schema already documents both parameters, and the description's '11-character id' and continuation_token phrasing only restate that. Per the baseline rule for full coverage, 3 is appropriate — no meaningful semantic value is added beyond the schema.

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?

The description opens with a specific verb+resource ('Retrieve video comments') and immediately scopes it ('top-level & replies') and anchors it to an input ('a YouTube video by its 11-character id'). No sibling in the list handles video comments, so an agent can tell this apart from youtube_captions, youtube_transcript, or youtube_video without opening a schema.

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 (call it to get comments for a given video) and there is one concrete instruction — leave continuation_token empty for the first page. However, it never states when to prefer this over related content tools (captions/transcript) or any precondition on the video id, so guidance is only implicit.

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