Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage YouTube comments

manage_youtube_comments
Destructive

Create, reply to, edit, delete, or moderate comments on the connected channel's YouTube videos, with a preview and approval step before anything is sent.

Instructions

Comments on the connected channel's videos, as the channel. create (text, and parent_id to reply or video_id for a new comment; idempotency_key); edit (comment_id, text: only the channel's own comments); delete (comment_id, own comments only, needs confirm); moderate (comment_ids up to 50, status published|heldForReview|rejected, ban_author; rejected or banning needs confirm). Read them with youtube_read comments. Every call spends the account's daily YouTube allowance (free plan 200 units, paid plans 2,000; resets at midnight Pacific time; youtube_read quota shows what is left): reads cost about 1 unit, most writes 50, captions 400-450, so batch reads and avoid needless writes. Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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": {
      "action": "<action>",
      "user": "<user>"
    },
    "name": "manage_youtube_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name with YouTube connected.
actionYes
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. See the description for each action's fields. Leave out what you do not want to change.
confirmNoThe API's own confirmation for deletions and other changes that cannot be undone. Set it to true only after the user has approved that exact change; without it those actions are refused and nothing changes.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
comment_idNoedit / delete: the comment.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (destructiveHint=true, openWorldHint=true), it discloses quota economics the annotations cannot: daily allowance of 200 vs 2,000 units, midnight Pacific reset, approximate unit costs per operation, and guidance to batch reads and avoid needless writes. It also explains the two-step preview/confirm safety protocol and that a preview sends nothing.

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?

Content is front-loaded: the action vocabulary comes first, then quota, then the approval protocol. It is dense, and the long nested parenthetical for create/edit/delete/moderate field lists takes effort to parse, but nearly every clause carries operational information.

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?

For a destructive, multi-action, open-world tool with a free-form params object, the description covers action selection, per-action fields, confirmation gating, and rate/quota limits. An output schema exists, so the absence of return-value documentation is not a gap.

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 83%, so the baseline is 3. The description does add field-level meaning the schema cannot supply for the free-form `params` bag (parent_id vs video_id, idempotency_key, comment_ids up to 50, status values, ban_author), but it lists these compactly in a single parenthetical rather than explaining formats or defaults.

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 opens with a specific verb set and resource: create/edit/delete/moderate comments on the connected channel's videos, acting as the channel. It explicitly routes read operations to the sibling youtube_read, so an agent can separate this mutation tool from the read tool without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use routing ('Read them with youtube_read comments') and a full prerequisite workflow: call first without `confirmed` to preview, show the user what will be sent, then repeat with `confirmed: true` only after approval. It also states per-action preconditions (edit/delete own comments only, delete requires `confirm`, rejected/ban needs `confirm`).

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