Skip to main content
Glama
CainDez
by CainDez

gitee_delete_all_issue_labels

Remove all labels from a Gitee issue to clear its label set. Specify the repository owner, repo name, and issue number.

Instructions

Remove all labels from an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner
repoYesRepository path name
numberYesIssue number
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior. It states 'Remove all labels' but does not indicate that this is a destructive operation (deleting all labels), any required permissions, or whether the action is reversible. The name implies deletion, but the description lacks critical behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that concisely states the purpose. It is front-loaded with the key action and resource. However, it could benefit from more structure or bullet points for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is destructive (removes all labels), the description is incomplete. It does not mention the irreversible nature, any output format, or behavioral side effects. With no output schema or annotations, the description should provide more context for safe usage.

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?

Schema coverage is 100% with three parameters (owner, repo, number) each having descriptions. The description adds no additional meaning beyond the schema, meeting the baseline for high coverage.

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 'Remove all labels from an issue' clearly states the action (remove all labels) and the resource (an issue). It distinguishes from sibling tools like gitee_delete_issue_label (removes a single label) and gitee_replace_issue_labels (replaces with new set).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus alternatives. It does not mention that it removes ALL labels, which is a destructive operation, nor does it provide context about prerequisites or 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/CainDez/mcp-gitee'

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