Skip to main content
Glama

delete_issue_label

Remove a label from an issue in an AtomGit repository to organize and categorize project tasks effectively.

Instructions

Remove a label from an issue in a repository

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesRepository owner, typically referred to as 'username'. Case-insensitive.
repoYesRepository name. Case-insensitive.
issue_numberYesIssue number
nameYesLabel name

Implementation Reference

  • Core handler function that executes the logic to delete an issue label by making a DELETE request to the AtomGit API.
    export async function deleteIssueLabel(
      owner: string,
      repo: string,
      issue_number: number,
      name: string
    ) {
      return atomGitRequest(
        `https://api.atomgit.com/repos/${encodeURIComponent(owner)}/${encodeURIComponent(repo)}/issues/${encodeURIComponent(issue_number)}/labels/${encodeURIComponent(name)}`,
        {
          method: "DELETE",
        }
      );
    }
  • Zod schema defining the input parameters (owner, repo, issue_number, name) for the delete_issue_label tool.
    export const DeleteIssueLabelSchema = z.object({
      owner: z.string().describe("Repository owner, typically referred to as 'username'. Case-insensitive."),
      repo: z.string().describe("Repository name. Case-insensitive."),
      issue_number: z.number().describe("Issue number"),
      name: z.string().describe("Label name"),
    });
  • index.ts:192-196 (registration)
    Registration of the delete_issue_label tool in the MCP server's list of tools, specifying name, description, and input schema.
    {
      name: "delete_issue_label",
      description: "Remove a label from an issue in a repository",
      inputSchema: zodToJsonSchema(label.DeleteIssueLabelSchema),
    },
  • MCP tool call handler that parses input arguments using the schema, invokes the deleteIssueLabel function, and returns the result.
    case "delete_issue_label": {
      const args = label.DeleteIssueLabelSchema.parse(request.params.arguments);
      const { owner, repo, issue_number, name } = args;
    
      const result = await label.deleteIssueLabel(owner, repo, issue_number, name);
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Remove') but doesn't clarify if this is a destructive operation, what permissions are required, how errors are handled (e.g., if the label doesn't exist), or what the response looks like. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core action ('Remove') and avoids redundancy, making it easy to parse quickly. Every part of the sentence earns its place by specifying the resource and context.

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's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., side effects, error handling) and output expectations, which are critical for safe and effective use. While the schema covers parameters well, the overall context for invoking this tool is insufficient.

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, clearly documenting all four parameters (owner, repo, issue_number, name) with details like case-insensitivity. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Remove') and target ('a label from an issue in a repository'), making the purpose immediately understandable. It distinguishes itself from siblings like 'create_issue_labels' or 'get_issue_labels' by specifying removal rather than creation or retrieval. However, it doesn't explicitly contrast with all siblings (e.g., 'assign_issue' also modifies issues), so it falls short of a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing existing labels or permissions), exclusions, or comparisons to siblings like 'create_issue_labels' for adding labels. Without such context, the agent must infer usage from the tool name alone.

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/kaiyuanxiaobing/atomgit-mcp-server'

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