Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

youtube_video_comment_replies

Retrieve replies to a specific YouTube video comment using a continuation token, then paginate through reply threads with each response token.

Instructions

youtube: Comment Replies. GET /v1/youtube/video/comment/replies. Get replies to a specific comment on a YouTube video. 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": {
      "continuationToken": "<continuationToken>"
    },
    "name": "youtube_video_comment_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
continuationTokenYesUse repliesContinuationToken from Comments, then continuationToken from each replies response to paginate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a non-trivial cost model: 1 credit on success, free on errors/blocked/timeout/invalid/cache hits, and not-found charged per published cost. That is genuinely useful. However, it says nothing about auth requirements, rate limits, or what a reply record contains, leaving meaningful behavioral gaps for a read tool with zero annotation coverage.

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?

Front-loaded with the tool name, endpoint, and purpose before the cost boilerplate. The cost sentence is somewhat verbose and generic across the API surface, but nothing is redundant enough to obscure the core instruction.

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

Completeness3/5

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

There is no output schema and no annotations, so the description is the only source of behavioral detail. It covers cost and pagination but omits the shape of returned replies and any indication of result ordering or limits, which an agent would want before calling.

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 coverage is 100% and the single parameter already documents the chaining pattern in its own description. The prose restates that same pagination flow rather than adding new meaning, so the baseline 3 applies.

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 replies to a specific comment on a YouTube video.' This distinguishes it from the sibling youtube_video_comments (top-level comments) by implication, though it never names that sibling explicitly. An agent can identify the operation without opening the schema.

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?

The description gives concrete pagination guidance: seed with repliesContinuationToken from Comments, then chain continuationToken from each replies response. It does not say when to prefer this over youtube_video_comments or what to do when a comment has no replies, so usage context is implied rather than stated.

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