Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_list_moderation_comments

Read-only

Lists selected-channel YouTube moderation threads with their available replies, letting you filter by held-for-review, likely spam, or published status and paginate results.

Instructions

List selected-channel moderation threads with available replies.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "youtube_list_moderation_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageTokenNoPage token from the nextPageToken of a previous response, to fetch the next page.
maxResultsNoMaximum number of items to return, 1-50; omit to use the tool default.
moderationStatusNoOnly list comments with this moderation status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / moderationStatus / description
      Added value: +"Only list comments with this moderation status."
    • addedInput schema / properties / pageToken / description
      Added value: +"Page token from the nextPageToken of a previous response, to fetch the next page."
  2. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

readOnlyHint=true already covers the safety profile, but the description adds little beyond it: "available replies" is undefined, and it omits that results are scoped to the authenticated user's channel, that moderationStatus defaults to something, or how pagination behaves.

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; its brevity is efficient, though it borders on under-specification rather than being tight.

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

Completeness2/5

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

For a tool with three optional parameters, an enum, and no output schema, the description never explains what a "thread" or its "replies" look like, which channel is queried, or what the default moderation status is — leaving real gaps an agent must guess at.

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 pagination and the moderationStatus enum are already fully documented in the schema; the description adds nothing about them, which is the baseline 3 for a fully-covered 3-param tool.

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

Purpose3/5

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

It has a verb ("List") and a resource ("moderation threads"), but the qualifiers "selected-channel" and "with available replies" are ambiguous and do not cleanly distinguish it from siblings such as youtube_list_channel_comment_threads or youtube_get_moderation_comment.

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?

There is no statement of when to use this rather than youtube_get_moderation_comment, youtube_list_channel_comment_threads, or youtube_get_comments, and no prerequisites (such as needing to be the channel owner/moderator) are given.

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