Skip to main content
Glama
tuitamogamer-gpt

youtube-mcp-server

by tuitamogamer-gpt
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Set Comment Moderation Status

youtube_set_comment_moderation
Idempotent

Moderate YouTube comments by approving, holding for review, or rejecting them. Optionally ban comment authors in bulk.

Instructions

Sets the moderation status of one or more comments. Can optionally ban the comment author(s).

Args

  • commentId (string, required) — ID of the comment to moderate. Accepts a comma-separated list of IDs to moderate multiple comments in one call (e.g. "id1,id2,id3").

  • moderationStatus ("published" | "heldForReview" | "rejected", required) — Target moderation state:

    • published: approve and make public.

    • heldForReview: hold for manual review.

    • rejected: reject (hide) the comment.

  • banAuthor (boolean, default false) — If true, bans the author(s) from commenting on the channel.

Returns

{ "moderated": true, "commentIds": ["string"], "moderationStatus": "string", "banAuthor": false }

Examples

  • Approve a comment: { "commentId": "UgxABC123", "moderationStatus": "published" }

  • Reject and ban: { "commentId": "UgxXYZ,UgxFOO", "moderationStatus": "rejected", "banAuthor": true }

Errors

  • 400 if moderationStatus is invalid.

  • 403 if the comment(s) do not belong to the authenticated channel's videos, or quota is exceeded.

  • 404 if a comment ID does not exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commentIdYesID of the comment to moderate. Comma-separate multiple IDs to moderate in bulk.
moderationStatusYes"published" to approve, "heldForReview" to hold, "rejected" to reject/hide.
banAuthorNoIf true, bans the comment author(s) from the channel.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations indicate idempotent and non-destructive. Description adds substantial behavioral details: bulk moderation via comma-separated IDs, specific moderation statuses, optional author banning, return format, and error codes. No contradiction with annotations.

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?

Well-structured with separate Arg/Returns/Examples/Errors sections. Comprehensive but not overly verbose. A minor redundancy with schema parameter descriptions, but overall efficient.

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?

Complete coverage: explains all parameters, return value JSON, error codes, and multiple examples. Lacks output schema but the description provides full return type. Sufficient for agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema details are 100% covered, but the description adds deeper meaning: explains comma-separated IDs for bulk, enumerates moderation statuses with descriptions, clarifies default for banAuthor, and provides concrete examples. Goes well beyond the schema.

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 sets the moderation status of comments, with optional author banning. It distinguishes from sibling tools like youtube_delete_comment and youtube_mark_comment_as_spam, which handle related but distinct actions.

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?

Provides clear usage context with examples and error cases, but does not explicitly state when not to use this tool or mention alternatives beyond the sibling list. Slightly lacking exclusion guidance.

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