Skip to main content
Glama
harshmaur

GitLab MCP Server

by harshmaur

delete_issue_link

Remove a link between two issues in GitLab by specifying the project, issue, and link ID to disconnect related issues.

Instructions

Delete an issue link

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesProject ID or URL-encoded path
issue_iidYesThe internal ID of a project's issue
issue_link_idYesThe ID of an issue relationship

Implementation Reference

  • Zod input schema for the 'delete_issue_link' tool. Defines required parameters: project_id (string), issue_iid (number), issue_link_id (number). Used for input validation in the MCP tool implementation.
    export const DeleteIssueLinkSchema = z.object({
      project_id: z.string().describe("Project ID or URL-encoded path"),
      issue_iid: z.number().describe("The internal ID of a project's issue"),
      issue_link_id: z.number().describe("The ID of an issue relationship"),
    });
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. It doesn't indicate that this is a destructive operation (implied by 'delete'), specify permissions required, describe error conditions, or explain what happens upon deletion (e.g., whether it's irreversible). This leaves critical behavioral traits undocumented.

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

Conciseness2/5

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

While concise, the single sentence 'Delete an issue link' is under-specified rather than efficiently informative. It fails to front-load critical details like scope or context, making it inadequate despite its brevity. Conciseness should not come at the cost of essential clarity.

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

Completeness1/5

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

For a destructive tool with no annotations and no output schema, the description is severely incomplete. It lacks information on behavioral impact, error handling, return values, and usage context. Given the complexity of deletion operations and the absence of structured safety hints, this description fails to provide adequate contextual guidance.

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 description coverage is 100%, so the schema fully documents all three parameters (project_id, issue_iid, issue_link_id). The description adds no parameter semantics beyond what's in the schema, but the baseline score of 3 is appropriate when the schema handles parameter documentation effectively.

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

Purpose2/5

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

The description 'Delete an issue link' is a tautology that merely restates the tool name without adding specificity. It doesn't distinguish this tool from sibling tools like 'delete_issue' or 'delete_label', nor does it clarify what an 'issue link' represents in this context (e.g., relationships between issues).

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

Usage Guidelines1/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 an existing issue link), exclusions, or relationships with sibling tools like 'create_issue_link', 'get_issue_link', or 'list_issue_links', leaving the agent with no contextual usage information.

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/harshmaur/gitlab-mcp'

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