Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_find_comment_reply

Read-only

Find an exact reply from a selected channel under a specific top-level YouTube comment by matching reply text.

Instructions

Exhaustively find an exact selected-channel reply under one immutable parent comment.

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": {
      "parentId": "<parentId>",
      "text": "<text>"
    },
    "name": "youtube_find_comment_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesReply text to match, up to 10000 characters.
parentIdYesID of the top-level comment whose replies are searched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / parentId / description
      Added value: +"ID of the top-level comment whose replies are searched."
    • addedInput schema / properties / text / description
      Added value: +"Reply text to match, up to 10000 characters."
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds one real behavioral signal — 'exhaustively' implies a full scan of the parent's replies (potentially slow/paginated) — but says nothing about what happens on no-match, whether it errors or returns empty, or how early it can short-circuit.

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?

A single front-loaded sentence with no filler. It is arguably over-compressed: two words ('immutable', 'selected-channel') carry meaning the reader must guess at, which is terseness rather than clarity.

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?

The tool is simple (2 required params, no nesting), but with no output schema the description should say what comes back on a hit versus a miss. It implies an exhaustive search without warning about cost or describing the return, leaving a real gap for an agent deciding whether to call it.

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%, so the baseline is 3. The description does add that matching on 'text' is exact and that the reply must belong to a specific channel, which is meaning beyond the schema's 'reply text to match' — but 'selected-channel' is too ambiguous to rely on.

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?

The verb-resource pair (find reply) is specific, and the scoping qualifiers (one immutable parent comment) narrow it meaningfully versus siblings like youtube_get_comments. However, 'selected-channel' and 'immutable' are cryptic — it's unclear whether 'selected-channel' means a reply authored by the authenticated channel or scoped by a channel argument (there is none in the schema), which blunts differentiation.

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 statement of when to use this instead of youtube_get_comments, youtube_list_channel_comment_threads, or youtube_get_moderation_comment, all of which touch comment data. No prerequisites, no note that it is a scan-style lookup rather than a listing.

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