Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

youtube_post_comment_reply

Destructive

Post a comment on a YouTube video, or reply to an existing comment. Pass video_id for a top-level comment, OR parent_comment_id to reply. AI-disclosure suffix appended automatically when configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesComment body. 1-10000 chars. AI-disclosure suffix may be auto-appended.
video_idNoBare videoId or 'youtube:video:<id>' — for a top-level comment.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
parent_comment_idNoBare commentId or 'youtube:comment:<id>' — for a reply.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the full safety profile (readOnlyHint=false, destructiveHint=true, idempotentHint=false, openWorldHint=true), so the bar is lower. The description still adds non-obvious behavioral context beyond annotations: an AI-disclosure suffix is auto-appended 'when configured', meaning the submitted text may be modified server-side. It does not mention auth requirements, rate limits, or failure behavior.

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?

Three short sentences, zero filler, and the core action is front-loaded. Each sentence carries distinct information: the action, the mode routing, and the side effect on the text.

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 4-parameter mutation tool with no output schema and rich annotations, the description covers the two invocation paths and the content-mutation side effect adequately. It leaves unstated whether both id fields can be supplied together, what the returned comment looks like, and any posting limits.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds real value on top of the schema by stating the mutual-exclusivity/OR relationship between video_id and parent_comment_id, which the per-property schema descriptions state only in isolation.

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 states a specific verb and resource ('Post a comment on a YouTube video, or reply to an existing comment') and cleanly separates the two operating modes. It does not explicitly name the sibling it is not (e.g., youtube_moderate_comment or youtube_list_comments), but the post-vs-read/moderate distinction is unambiguous from the wording.

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?

It gives explicit branching guidance for invocation: pass video_id for a top-level comment OR parent_comment_id to reply. What is missing is any when-not-to-use guidance or comparison against sibling tools like youtube_moderate_comment or youtube_list_comments, so it falls short of a 5.

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

All dialogbrain toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources