Skip to main content
Glama

youtube_moderate_comment

Apply a moderation status to a YouTube comment. Allowed status values: heldForReview, published, rejected, spam. Costs 50 quota units.

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": {
      "comment_id": "<comment_id>",
      "status": "<status>"
    },
    "name": "youtube_moderate_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYesOne of: heldForReview, published, rejected, spam.
account_idNoWhich connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.
comment_idYesBare commentId OR 'youtube:comment:<id>'.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Which connected YouTube channel to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds genuinely useful context by disclosing the 50-unit quota cost, which is not in any structured field. However, it does not explain the practical effect of each status (e.g., whether 'rejected' or 'spam' hides the comment from view) or whether a prior status can be restored.

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?

Two tight sentences with no filler; the core action is front-loaded and the operational constraint (quota cost) follows immediately. Every clause carries information, and the allowed-value list is compact enough not to bloat the definition.

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

Completeness3/5

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

For a mutation tool with annotations, full schema coverage, and no output schema, the description is close to sufficient. The main gap is semantic: an agent cannot tell from this text what each moderation status actually does to the comment, which is the key decision input for a moderation call. Return behavior is not described, but no output schema exists to lean on.

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%, and the schema itself already documents account_id omission rules, workspace override behavior, and the accepted comment_id formats in detail. The only parameter information in the description is the list of allowed status values, which duplicates the status field's enum-style schema description rather than adding meaning. Baseline 3 applies since the schema does the heavy lifting.

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?

The description opens with a specific verb and resource: 'Apply a moderation status to a YouTube comment', which is clearly distinct from deleting a comment or posting a reply. It stops short of explicitly naming those sibling tools as alternatives, so an agent must infer the boundary rather than read it.

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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. Nothing tells the agent whether moderation should be used to hide a comment versus youtube_delete_comment to remove it, nor when a status should be heldForReview instead of rejected. The usage is only implied by the tool name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.