Skip to main content
Glama

Vee3

by io.github.Vee3io

youtube.video_comments

Fetch top-level comments for a public YouTube video by its 11-character video id.

Returns comment text, author summary, vote and reply counts, pinned status, total comment count, and cursorNext for the next page.

Use sort_by to choose comment order:

  • sort_by: Top comments, Newest first

Sort values are matched case-insensitively.

Use cursor with the same video_id to paginate: pass cursorNext from a prior response. sort_by and cursor cannot be combined.

Cost = 15 tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cursorNoPagination cursor from a previous response cursorNext field.
sort_byNoComment sort order. One of: Top comments, Newest first.
video_idYesYouTube video id (11 characters, not a URL).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentsNoTop-level comments for the current page and sort order. Additional provider-specific fields may appear on each entry.
cursorNextNoCursor for the next comments page, when available.
totalCommentsCountNoTotal number of comments on the video.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses the return fields, pagination mechanism, sort options with case-insensitivity, and token cost. It does not discuss error handling or page size limits, but these are not critical for typical use. The added detail on constraints and return data surpasses what annotations would typically cover.

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?

The description is well-structured and front-loaded with the purpose. It uses short, clear sections for returns, sort_by, cursor, and cost. Every sentence provides useful information without redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers all critical aspects: purpose, required input format, return field summary, pagination via cursor, sort options with constraints, and cost. Since an output schema exists, the description need not detail every return field, but it still provides a concise overview, making the tool self-contained and easy to use.

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 adds meaningful value beyond the schema: it specifies that cursor requires the same video_id, that sort_by and cursor are mutually exclusive, and that sort values are case-insensitive. These constraints are not present in the input schema, enhancing the agent's ability to invoke the tool correctly.

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 and resource: 'Fetch top-level comments for a public YouTube video by its 11-character video id.' This clearly distinguishes the tool from sibling tools like youtube.video_details and tiktok.video_comments by specifying platform (YouTube) and scope (top-level comments).

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?

The description provides clear contextual prerequisites (public video, 11-character ID) and usage constraints (sort_by and cursor cannot be combined; cursor must use same video_id). However, it does not explicitly mention alternatives or exclusions relative to sibling tools, though the purpose itself makes the intended use obvious.

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

All Vee3 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a distinct purpose, further clarified by group prefixes and clear descriptions. Within each group, tools perform different operations (e.g., domains.lookup vs. domains.whois vs. domains.rdap) with no ambiguity.

Naming Consistency5/5

All tools follow a consistent group.tool_name pattern using snake_case. The naming is predictable and uniformly applied across all groups.

Tool Count4/5

78 tools is high, but the server aggregates multiple distinct API domains (11 groups). Each group has a reasonable number of tools, typically under 10, with TikTok having 17. The count reflects breadth, not bloat.

Completeness5/5

Each domain's tool set covers the primary expected operations (e.g., search, details, reviews, metrics, user info). There are no obvious gaps for read-only analytical use; features like posting are likely out of scope.

Resources