Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List YouTube video comments

youtube_video_comments_list
Read-onlyIdempotent

Retrieve comments from a YouTube video by URL. Supports pagination and sorting to analyze audience feedback and engagement.

Instructions

List comments on a YouTube video by URL. Requires url. Returns a list (use cursor when paginated). Pass the video link or 11-character id in url, e.g. {"url":"dQw4w9WgXcQ"}; there is no videoId field.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "youtube_video_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Link to the YouTube video whose comments should be listed.
orderNoComment sort order. `top` returns highest-ranked comments; `newest` returns the most recent comments.
cursorNoOpaque cursor from a previous response to fetch the next page.
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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. Beyond that, the description adds real behavioral value: return shape ('Returns a list'), pagination mechanism via cursor, and the fact that only top-level comments for one video are returned.

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 tight sentences, all front-loaded with the requirement first, then the return shape, then the input format. The inline JSON example earns its place by showing the id-only form, though the phrasing of the last clause is slightly awkward.

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?

With 6 params at full schema coverage, no output schema, and complete annotations, the description covers what an agent needs to call it correctly: required input, accepted formats, and pagination. It does not describe page size or comment fields, which is a minor gap for a read-only list tool.

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 coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: `url` accepts either a full video link or an 11-character id, and it explicitly warns there is no `videoId` field. That directly prevents a common malformed call.

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 description opens with a specific verb+resource: 'List comments on a YouTube video by URL.' It is clear what the tool retrieves, but it does not distinguish itself from the sibling youtube_video_comments_replies_list, which the agent must infer covers reply threads.

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?

It states the prerequisite ('Requires `url`') and notes cursor-based pagination for follow-up calls, so invocation context is present. However, it never says when to prefer this over the replies or analysis siblings, leaving alternative selection entirely implicit.

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