Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_video_comments

Retrieve comments from a YouTube video by URL and paginate through results with a continuation token to collect top or newer comments.

Instructions

youtube: Comments. GET /v1/youtube/video/comments. Provide one of: url, continuationToken. Get comments from a video. Can only get 1k top comments and about 7k new comments. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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

Input Schema

NameRequiredDescriptionDefault
urlYesYouTube video URL
orderNoOrder of comments
continuationTokenNoUse continuationToken from the previous response to get the next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does notable work: it discloses the retrieval ceiling (about 1k top comments, roughly 7k new comments), the 1-credit success charge, and that errors, blocked, timed-out, invalid, and cached requests cost nothing. It does not cover auth requirements or rate limiting, which keeps it below a 5.

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 operative content — resource, pagination hint, result caps — comes early, but the leading "youtube: Comments. GET /v1/youtube/video/comments." duplicates the tool name and route with no added meaning. The closing two sentences on billing edge cases are accurate but dense and partially redundant with each other.

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 three-parameter read tool with 100% schema coverage and no output schema, the description supplies the limits an agent needs to know before calling: pagination via continuationToken, result caps, and cost behavior. The one meaningful gap is the undocumented `order` parameter and any hint about the shape of the returned comments.

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 baseline is 3, and the description only restates the url/continuationToken choice already visible in the schema. The `order` parameter is never mentioned in the description, and "provide one of" sits slightly at odds with the schema marking url as required.

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 — "Get comments from a video" — plus the underlying route GET /v1/youtube/video/comments, so the agent knows exactly what it retrieves. It does not name the sibling youtube_video_comment_replies or explain the top-level-vs-reply distinction, so differentiation is left to inference.

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?

"Provide one of: url, continuationToken" gives a usable invocation condition and implicitly tells the agent to reuse a prior token for pagination. However, there is no explicit when-to-use/when-not guidance against alternatives such as youtube_video_comment_replies, so the agent must infer routing.

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