Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_get_comments

Read-only

List public comment threads for a specific YouTube video. Retrieve and analyze viewer feedback directly using the video ID.

Instructions

List public comment threads for a specific video.

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": {
      "videoId": "<videoId>"
    },
    "name": "youtube_get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoIdYesYouTube video ID (11 characters), e.g. dQw4w9WgXcQ.
maxResultsNoMaximum number of items to return, 1-50; omit to use the tool default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / maxResults / description
      Added value: +"Maximum number of items to return, 1-50; omit to use the tool default."
    • addedInput schema / properties / videoId / description
      Added value: +"YouTube video ID (11 characters), e.g. dQw4w9WgXcQ."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already declares the safety profile, so the bar is lower. The description does add that only 'public' threads are returned, which is meaningful (moderation-held comments excluded), but says nothing about ordering, pagination, or whether replies are inlined.

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?

A single front-loaded sentence with no filler; the scope qualifier comes before any implied behavior.

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?

No output schema exists, so the description could say more about what comes back (threads with replies, pagination). Still, for a simple read-only list with fully documented params and a safety annotation, an agent has enough to call it correctly.

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 both parameters carry their own descriptions including the 11-character ID format and the 1-50 range. The description adds no parameter-level information beyond the schema, so 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?

A clear verb plus resource plus scope: 'List public comment threads for a specific video.' The 'for a specific video' clause implicitly separates it from channel-wide or moderation siblings, though it never names 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?

Usage is implied by the video-scoped framing, but there is no explicit guidance on when to prefer this over youtube_list_channel_comment_threads, youtube_list_moderation_comments, or youtube_find_comment_reply, and no prerequisites (auth, public-only constraint) are 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