gitee_delete_gist_comment
Remove a comment from a specified Gitee gist by providing the gist ID and comment ID.
Instructions
Delete a gist comment
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| gist_id | Yes | Gist ID | |
| id | Yes | Comment ID |
Remove a comment from a specified Gitee gist by providing the gist ID and comment ID.
Delete a gist comment
| Name | Required | Description | Default |
|---|---|---|---|
| gist_id | Yes | Gist ID | |
| id | Yes | Comment ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a destructive action but provides no details on authorization, reversibility, or side effects. No annotations are provided to supplement, leaving a transparency gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear sentence with no unnecessary words. It is appropriately front-loaded and efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete operation with no output schema, the description is minimally sufficient but lacks behavioral context that would aid an agent, such as failure scenarios or permissions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with basic parameter descriptions ('Gist ID', 'Comment ID'). The description adds no additional meaning beyond the schema, so baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Delete a gist comment' clearly states the verb and resource. However, it does not differentiate from sibling tools like gitee_delete_issue_comment, limiting context.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool or when to avoid it. Alternatives are not mentioned, and no context is provided for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CainDez/mcp-gitee'
If you have feedback or need assistance with the MCP directory API, please join our Discord server