Skip to main content
Glama
Sign In
ttpears

GitLab MCP Server

by ttpears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Issue Context

get_issue_context
Read-onlyIdempotent

Bundles an issue’s body, notes, related and closing merge requests, and linked issues into one call, so you can investigate GitLab issues without fanning out across multiple queries.

Instructions

Bundle issue body, all notes (paginated up to maxNotes), related merge requests (mentioning), closing merge requests, linked issues (relates_to/blocks/is_blocked_by) into a single call. Use this instead of fanning out across get_issues + get_notes + search_merge_requests when investigating an issue.

Input Schema

NameRequiredDescriptionDefault
iidYesIssue IID (the number shown in the GitLab UI)
maxNotesNoCap on notes fetched. Default 100.
projectPathYesFull project path (e.g. "my-group/my-project")
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)
includeSystemNotesNoInclude system-generated notes (label changes, assignment events). Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / userCredentials / anyOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "accessToken": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "gitlabUrl": {
-        "format": "uri",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "accessToken": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "gitlabUrl": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
  2. Addedv1.15.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so safety is covered; the description adds real value by disclosing the aggregation behavior, the maxNotes pagination cap, and the scope of 'related' MRs (mentioning only) versus closing MRs. It stops short of describing behavior when the issue is missing or whether notes are truncated silently, so not a 5.

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?

Two sentences, both dense with information: the first front-loads what is returned, the second immediately routes the agent away from the fan-out alternative. No filler.

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?

With no output schema, the description usefully enumerates the response contents and relation types, which is the main thing an agent needs to know. Errors or behavior on a nonexistent/restricted issue are not addressed, a minor gap for a 5-param read tool.

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 all five parameters including maxNotes and includeSystemNotes are already documented in the schema. The description only alludes to the maxNotes cap, adding marginal meaning beyond the schema. Baseline 3 is appropriate.

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?

States a specific aggregation verb and enumerates exactly what is bundled: issue body, notes, related/closing merge requests, linked issues with relation types. This is clearly distinguishable from get_issues, get_notes, and search_merge_requests, which return only one slice each.

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

Usage Guidelines5/5

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

Explicitly says to use this 'instead of fanning out across get_issues + get_notes + search_merge_requests when investigating an issue', naming the alternatives and the condition that selects this tool. Little is left to inference.

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