Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

List Comment Threads

youtube_list_comment_threads
Read-onlyIdempotent

Retrieve top-level comment threads for a YouTube video or channel. Filter by search terms, order by time or relevance, and paginate through results.

Instructions

Retrieves a page of top-level comment threads for a YouTube video or channel.

Args

  • videoId (string, optional) — ID of the video whose comment threads to list.

  • channelId (string, optional) — Channel ID; lists all threads related to that channel (includes video comments and channel comments).

  • Exactly one of videoId / channelId must be supplied.

  • order ("time" | "relevance", default "time") — Sort order.

  • searchTerms (string, optional) — Filter threads containing this text.

  • maxResults (1–50, default 25) — Number of threads per page.

  • pageToken (string, optional) — Cursor returned from a previous call to fetch the next page.

  • response_format ("markdown" | "json", default "markdown") — Output format.

Returns

{
  "threads": [
    {
      "id": "string",
      "authorDisplayName": "string",
      "text": "string",
      "likeCount": 0,
      "publishedAt": "ISO-8601",
      "updatedAt": "ISO-8601",
      "totalReplyCount": 0,
      "replies": [ { "id": "string", "authorDisplayName": "string", "text": "string" } ]
    }
  ],
  "nextPageToken": "string | null"
}

Examples

  • List the first 10 comment threads on a video: { "videoId": "dQw4w9WgXcQ", "maxResults": 10 }

  • Page through channel comments: { "channelId": "UCxxxxxxx", "pageToken": "CAUQAA" }

Errors

  • 400 if neither or both of videoId / channelId are provided.

  • 403 if comments are disabled on the video or quota is exceeded.

  • 404 if the video or channel does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
videoIdNoVideo ID whose comment threads to list. Exactly one of videoId/channelId required.
channelIdNoChannel ID; lists all threads related to the channel. Exactly one of videoId/channelId required.
orderNoSort order: "time" (newest first) or "relevance".time
searchTermsNoOptional text filter; only threads containing this string are returned.
maxResultsNoNumber of threads per page (1–50, default 25).
pageTokenNoPagination cursor from a previous response's nextPageToken.
response_formatNoOutput format: "markdown" (default) or "json".markdown
Behavior4/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds useful behavioral insights beyond annotations, such as error conditions (400 if neither/both IDs, 403 if comments disabled or quota exceeded, 404 if resource not found) and the return structure. This provides sufficient transparency for safe agent behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections (Args, Returns, Examples, Errors) and is front-loaded with a concise summary. Every sentence adds value; there is no repetition or fluff. It's appropriately sized for the tool's complexity.

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

Completeness5/5

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

Given the tool has 7 parameters (none required), 100% schema coverage, and no output schema, the description covers all essential aspects: usage constraints, parameter details, return format with example, and common errors. It is comprehensive enough for an agent to correctly invoke and interpret results.

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 the schema documents all parameters. The description adds value by clarifying the mutual exclusivity requirement for videoId and channelId, listing the default for order, and providing a full JSON example of the return structure (not in schema). This goes beyond the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves a page of top-level comment threads for a YouTube video or channel, explicitly mentioning the two mutually exclusive IDs (videoId, channelId). This distinguishes it from siblings like youtube_list_comment_replies (which gets replies for a specific thread) and youtube_create_comment_thread (which creates).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear instructions on how to use the tool: exactly one of videoId or channelId must be supplied, with explanations of what each does. It includes examples for listing by video and paging through channel comments. However, it does not explicitly mention when not to use this tool or suggest alternatives like youtube_list_comment_replies for replies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tuitamogamer-gpt/youtube-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server