Skip to main content
Glama

delete_comment

DestructiveIdempotent

Delete a comment from a Huly issue. This action is irreversible.

Instructions

Delete a comment from a Huly issue. This action cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectYesa string that will be trimmed
commentIdYesa string that will be trimmed
issueIdentifierYesa string that will be trimmed
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds 'cannot be undone', which reinforces the destructive nature but adds no other behavioral context such as authorization requirements or side effects. Since annotations cover the key behavioral traits, the description provides marginal additional value.

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 sentences with no fluff. The first sentence states the purpose, the second adds the critical irreversibility warning. Information is front-loaded and efficient.

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 delete operation, the description covers purpose and irreversibility. No output schema is needed. Parameters are documented in schema (though poorly). The description is largely complete, but could include more context like 'Use with caution' or 'Only delete comments you created'.

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

Parameters2/5

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

The input schema has 3 required parameters, all with minimal descriptions ('a string that will be trimmed'). The tool description does not add any meaning beyond the schema, such as explaining what each parameter represents or how to obtain them. Schema coverage is 100% but descriptions are poor, and the description fails to compensate.

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 'Delete' and the resource 'a comment from a Huly issue'. It distinguishes from sibling tools like 'update_comment' and other delete operations.

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 warns that the action cannot be undone, implying careful use, but provides no explicit guidance on when to use this tool versus alternatives like delete_issue or update_comment. No comparison with other tools is given.

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/dearlordylord/huly-mcp'

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