Skip to main content
Glama
kud
by kud

update-comment

Edit a YouTube comment you posted by providing its comment ID and new text. Update the content of an existing comment.

Instructions

Edit the text of a comment you posted. Costs 50 quota units.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesNew comment text
commentIdYesComment ID
Behavior3/5

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

The description discloses the quota cost (50 units) and the ownership constraint, which are useful behavioral details beyond the schema. However, with no annotations, it does not mention permissions, reversibility, side effects, or expected response format, leaving significant transparency gaps for a mutation tool.

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?

One sentence, 11 words, front-loaded with the primary purpose. No extraneous information.

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 two-parameter mutation tool, the description covers the core action, ownership, and cost. The lack of output schema and annotations is partially compensated, but it omits success/failure behavior and return values, leaving some context gaps.

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?

The schema already provides 100% coverage with descriptions for both parameters (comment ID and new text). The description adds no additional semantic detail beyond the schema, so it meets the baseline but doesn't enhance understanding further.

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 'Edit the text of a comment you posted,' specifying the action (edit), resource (comment text), and ownership constraint. This distinguishes it from sibling tools like delete-comment or set-comment-moderation-status.

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?

The phrase 'you posted' implies the tool is limited to editing one's own comments, providing clear context. However, it does not explicitly mention when to avoid using it or suggest alternative tools for editing others' comments or performing other actions, so it falls short of explicit alternatives.

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/kud/mcp-youtube'

If you have feedback or need assistance with the MCP directory API, please join our Discord server