Skip to main content
Glama

video_comments

Read YouTube comments and filter them by keywords, sort order, replies, and character limits to extract relevant viewer feedback.

Instructions

Read YouTube comments. sort: 'top' or 'new'. replies=True adds replies (3 per thread). query: comma-separated terms; scans up to scan comments and returns only those containing any term (case-insensitive), e.g. query="broke,refund,scam". Each comment is cut to max_chars_each.

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": "video_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
scanNo
sortNotop
queryNo
repliesNo
max_commentsNo
max_chars_eachNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.8/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 disclose non-obvious behavior: replies add three replies per thread, query scans only up to `scan` comments so results are not exhaustive, matching is case-insensitive and OR-style across terms, and each comment is truncated. It omits any note on how max_comments interacts with the query filter (cap before or after filtering), which is the remaining behavioral ambiguity.

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?

Compact and front-loaded, with the core action first and per-parameter notes after; every clause carries information, and the query example earns its space. The telegraphic style (fragments, backticked `scan`) is efficient but slightly terse.

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?

An output schema exists, so return values need no explanation, and seven parameters with zero schema descriptions are mostly covered in prose. The missing piece is the max_comments/filter interaction, plus no statement about whether reads are rate-limited or paginated across the scan window.

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 description coverage is 0%, so the description must compensate and largely does: sort values ('top'/'new'), replies, query syntax with a concrete example, scan as a bounded search window, and max_chars_each truncation are all explained. Only max_comments (and the obvious url) go unexplained, leaving one gap out of seven.

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

Purpose4/5

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

States a specific verb and resource ('Read YouTube comments') and the domain is clearly distinct from siblings like video_transcript or video_info. It never explicitly contrasts with a sibling tool, so it stops short of a 5.

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 only implied: an agent can infer this is the tool for comment retrieval and that the query filter serves keyword triage. There is no explicit when-to-use/when-not-to-use guidance, and no pointer to alternatives such as transcribe_video when the agent actually needs spoken content.

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