Skip to main content
Glama
Sign In
gitlab mcp

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_issue

Read-only

Retrieve a single GitLab issue by project ID and issue IID; optionally return the full milestone or filter the JSON result with JMESPath.

Instructions

Get one issue. Slim nested milestone by default; full_response=true for the complete milestone. Use this for issue management. Use list_issues or my_issues to discover issues first.

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>"
    },
    "name": "get_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
jmespathNoOptional JMESPath expression filtering the JSON result before return.
issue_iidYesIssue IID
project_idYesProject ID or URL-encoded path
full_responseNoIf true, include the complete milestone (including description). Default is slim (id, iid, title, state, web_url).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.3.22
    • changedInput schema / properties / full_response / description
      Previous value: -"If true, include the complete milestone object, including its description, on the returned issue. Default returns the issue with a slim milestone (id, iid, title, state, web_url) to reduce token usage."New value: +"If true, include the complete milestone (including description). Default is slim (id, iid, title, state, web_url)."
    • changedInput schema / properties / issue_iid / description
      Previous value: -"The internal ID of the project issue"New value: +"Issue IID"
  2. Changed1 schema field changedv2.2.6
    • changedInput schema / properties / full_response / description
      Previous value: -"If true, return the complete issue object including the full milestone description. Default returns a slim milestone (id, iid, title, state, web_url) to reduce token usage."New value: +"If true, include the complete milestone object, including its description, on the returned issue. Default returns the issue with a slim milestone (id, iid, title, state, web_url) to reduce token usage."
  3. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  4. Changed1 schema field changedv2.1.30
    • addedInput schema / properties / full_response
      Added value: +{
+  "description": "If true, return the complete issue object including the full milestone description. Default returns a slim milestone (id, iid, title, state, web_url) to reduce token usage.",
+  "type": "boolean"
+}
  5. Addedv2.1.18
  6. Removedv2.1.14
  7. Addedv2.1.11
  8. Removedv2.1.10
  9. Changed2 schema fields changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / required
      Added value: +[
+  "project_id",
+  "issue_iid"
+]
  10. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds useful behavioral context by disclosing that the milestone is slimmed by default and that full_response=true is needed for the complete object. It does not describe error behavior for a missing issue or permission failures, but the added default-response detail is meaningful beyond the annotations.

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?

Three short sentences, front-loaded with the core action and the default return shape. The middle sentence ("Use this for issue management") is filler that does not earn its place.

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

Completeness4/5

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

For a simple read-only single-resource fetch with no output schema, the description covers the action, the default return shape, how to get the full version, and how to find issues first. Nothing critical for calling it correctly is missing, though error/not-found behavior is unstated.

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%, and each parameter (including full_response and jmespath) is documented in the schema itself. The description mentions full_response but repeats the schema's own wording rather than adding new semantics, so baseline 3 applies.

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 opens with a specific verb+resource ("Get one issue") and immediately states the returned shape (slim nested milestone by default), which separates it from list-oriented siblings. The only weak line is "Use this for issue management," which restates the obvious rather than narrowing scope.

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

Usage Guidelines4/5

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

It explicitly routes discovery to `list_issues` or `my_issues` "first," giving the agent a clear alternative and the condition that selects it. It stops short of stating when-not to use this tool (e.g., bulk retrieval) or any prerequisites such as project membership.

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

Deploy Server

Other Tools