Skip to main content
Glama

job_youtube_comments

Top comments on a YouTube 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": {
      "video_url": "<video_url>"
    },
    "name": "job_youtube_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_urlYespattern https://(www\.|m\.)?(youtube\.com/(watch\?v=|shorts/)|youtu\.be/)[A-Za-z0-9_-]{11}\S{0,100}
max_resultsNodefault 100, at most 1000

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full disclosure burden, yet it says nothing about ordering, pagination, whether replies are included, quota/rate costs, or whether an API key is needed. 'Top' is the only behavioral hint and it is undefined.

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

Conciseness3/5

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

The one-line fragment is short and front-loaded, but its brevity comes from omitting information rather than from efficiency. There is no wasted wording, yet it also has no structure to build on.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the agent is left without any picture of the return shape (author, text, like counts, reply nesting) or of result ordering. The input side is fully covered by the schema, but the output and behavior side is empty.

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 video_url's regex pattern and max_results' default (100) and cap (1000) are already documented in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The phrase 'Top comments on a YouTube video' identifies the resource (comments) and scope (top-ranked), so an agent can tell it is not job_youtube_transcript or job_youtube_search. However there is no verb and 'top' is left ambiguous (by likes? by relevance? chronological?), so the returned selection logic is unclear.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives such as job_youtube_transcript for spoken content. The agent must infer the use case entirely from the name and the two-word description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources