Skip to main content
Glama
Sign In

MCPTube

by org.dunamistech
OverviewDiscussionsAdmin

Get video comments

get_video_comments
Read-onlyIdempotent

Returns one full page of public comments for a YouTube video, ordered by top or newest. Use nextCursor for more comments or repliesCursor for replies on demand, keeping the same video and order.

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": {
      "url": "<url>"
    },
    "name": "get_video_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL or ID of a YouTube video (watch, youtu.be, shorts, live, embed or clip).
orderNoComment ordering. Default: top. Keep unchanged when using a cursor.
cursorNoOpaque nextCursor or repliesCursor. Keep the same video and order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful context about pagination and result scope: it returns one full page of public comments, and cursors are used for more comments or replies.

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 two tight sentences with the core purpose front-loaded. Every clause contributes useful information about page behavior, ordering, and cursor usage.

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?

For a three-parameter read-only tool with no output schema, the description covers the key behaviors: public comments, one-page results, ordering options, and cursor continuation. It is complete enough for an agent to invoke correctly.

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 schema already documents url, order, and cursor. The description adds meaningful semantic detail by distinguishing nextCursor for more comments and repliesCursor for replies, plus the constraint to keep the same video and order.

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 states a specific verb and resource: returns public comments for a YouTube video. It also clarifies scope by saying 'one full page' and specifying ordering by top or newest, making the tool's purpose unambiguous.

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?

It explains how to paginate using nextCursor and repliesCursor, and notes that the same video and order must be kept. It does not explicitly compare this tool to siblings like get_video_info or search_videos, so it falls short of full when/when-not guidance.

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

All MCPTube toolsInspect
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