Skip to main content
Glama

edit_comment

DestructiveIdempotent

Update the text of a specific comment on a Loom video by providing the comment ID, video ID, and new content.

Instructions

Edit an existing comment on a Loom video. Overwrites the comment text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYesThe comment ID
video_idYesThe Loom video ID the comment belongs to
contentYesThe new comment text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Description adds the key behavior 'Overwrites the comment text' beyond annotations. Annotations already indicate destructiveHint=true and idempotentHint=true, and the description complements these by specifying the overwrite action. No contradictions.

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?

The description is a single, front-loaded sentence that conveys the tool's purpose and behavior without extraneous words. Every word contributes meaning.

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?

The description, combined with annotations and schema, covers the essential aspects of the tool for a simple comment editing operation. It misses no critical information for this use case, though it could mention error handling or the fact that only text is affected.

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 input schema has 100% description coverage for all three parameters. The description does not add additional meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 the verb 'Edit' and the resource 'existing comment on a Loom video', and specifies the action 'Overwrites the comment text'. This distinguishes it from sibling tools like create_comment, delete_comment, and get_comments.

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 description does not provide explicit guidance on when to use this tool versus alternatives. However, the tool name and description imply its use for modifying existing comments. No exclusions or conditions are mentioned, which is acceptable given the tool's simplicity.

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/karbassi/mcp-loom'

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