Skip to main content
Glama
Sign In
YouTube MCP

YouTube MCP

by pratikgh0se
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

youtube_get_moderation_comment

Read-only

Read a single immutable YouTube comment by ID to reconcile moderation records. Use it to verify exact comment content before taking moderation action.

Instructions

Read one immutable comment by ID for exact moderation reconciliation.

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": {
      "commentId": "<commentId>"
    },
    "name": "youtube_get_moderation_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentIdYesYouTube comment ID, from the comment listing tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedInput schema / properties / commentId / description
      Added value: +"YouTube comment ID, from the comment listing tools."
  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?

The readOnlyHint annotation already establishes safe read behavior. The description adds that the comment is 'immutable' and frames the use case around exact moderation reconciliation, but it does not describe return behavior, error cases, or rate limits. With annotation coverage, this is adequate but not rich.

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 wasted words. The purpose and scope are stated immediately.

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?

For a simple one-parameter read tool with full schema coverage and readOnlyHint present, the description is largely complete. It could say more about the returned comment shape since there is no output schema, but the retrieval intent is clear.

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 the schema describes commentId as a YouTube comment ID from listing tools. The description only adds 'by ID,' so the schema does the substantive parameter documentation and the baseline of 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?

States a specific verb and resource: 'Read one immutable comment by ID,' with a clear moderation-reconciliation scope. It implicitly distinguishes itself from listing tools like youtube_list_moderation_comments by fetching a single comment, but does not explicitly name alternatives.

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?

The phrase 'for exact moderation reconciliation' implies the intended context, but there is no explicit guidance on when to choose this tool over siblings such as youtube_get_comments or youtube_list_moderation_comments. The schema notes the ID comes from listing tools, but the description itself does not route the agent.

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