Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List YouTube comment replies

youtube_video_comments_replies_list
Read-onlyIdempotent

Retrieves replies to a specific YouTube comment and returns paginated results using a cursor, enabling continued thread analysis and discussion review.

Instructions

List replies to a YouTube comment. Requires cursor. Returns a list (use cursor when paginated).

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": {
      "cursor": "<cursor>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_video_comments_replies_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorYesComment `repliesCursor` from Video Comments endpoint, or `page.nextCursor` to paginate replies.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint, so the safety profile is covered. The description adds the pagination mechanic and the hard cursor requirement, which is useful, but says nothing about invalid/expired cursor behavior or result size.

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?

Three short sentences, front-loaded with purpose, zero wasted prose. The parenthetical pagination note is slightly redundant with the schema's cursor description but small and harmless.

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?

For a simple read-only list tool with full schema coverage and no output schema, the definition is close to adequate but omits the crucial dependency: how an agent obtains a valid cursor before it can call this tool at all.

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 all four parameters including `cursor` and its `page.nextCursor` usage are already documented in the schema. The description merely restates the cursor requirement rather than adding syntax or format meaning beyond it.

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: "List replies to a YouTube comment." This distinguishes it from the sibling youtube_video_comments_list by scope (replies vs top-level comments), though it does not explicitly name that sibling or route the agent between them.

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?

Says it requires `cursor` and hints to use the cursor for pagination, which implies the correct usage context. However, it never tells the agent where to obtain the initial cursor (e.g., from the parent comment in youtube_video_comments_list), nor states any when-not-to-use condition.

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