GitLab MCP Server

get_issue_link

Retrieve a specific issue relationship link from GitLab projects using project ID, issue internal ID, and link ID to access connected issue data.

Instructions

Get a specific issue link

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "issue_iid": "<issue_iid>",
      "issue_link_id": "<issue_link_id>"
    },
    "name": "get_issue_link"
  }
}

Input Schema

Name	Required	Description
`project_id`	Yes	Project ID or URL-encoded path
`issue_iid`	Yes	The internal ID of a project's issue
`issue_link_id`	Yes	ID of an issue relationship

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.0.0Jan 3, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedNov 16, 2025

TDQS

C2.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get a specific issue link', implying a read-only operation, but does not specify whether authentication is required, if there are rate limits, what the output format is, or potential error conditions. For a tool with three required parameters and no output schema, this leaves critical behavioral traits undefined.

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 extremely concise with a single sentence: 'Get a specific issue link'. It is front-loaded and wastes no words, though this brevity contributes to underspecification in other dimensions. Every word serves a purpose, earning a high score for conciseness despite overall inadequacy.

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 (3 required parameters, no annotations, no output schema), the description is incomplete. It lacks context on what an 'issue link' is, how it differs from other issue-related tools, what the return value includes, and any behavioral constraints. Without annotations or output schema, the description fails to provide sufficient information for effective tool use.

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%, with clear parameter descriptions in the input schema (e.g., 'Project ID or URL-encoded path', 'The internal ID of a project's issue'). The tool description adds no additional meaning about parameters beyond what the schema provides. According to guidelines, when schema coverage is high (>80%), the baseline score is 3, which applies here as the description does not compensate or elaborate further.

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 'Get a specific issue link' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'Get' and resource 'issue link' but lacks specificity about what an 'issue link' represents (e.g., a relationship between issues) or how it differs from sibling tools like 'list_issue_links' or 'create_issue_link'. This minimal phrasing fails to clarify the tool's distinct purpose within the server's ecosystem.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, such as needing an existing issue link ID, or contrast it with sibling tools like 'list_issue_links' (for listing multiple links) or 'get_issue' (for general issue details). Without any usage context, an agent cannot determine appropriate scenarios for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.