Skip to main content
Glama
Sign In
GitLab MCP Server

GitLab MCP Server

by ttpears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

User Merge Requests

get_user_merge_requests
Read-onlyIdempotent

Retrieve merge requests authored by or assigned to a specific GitLab user, with filters for state, project, and pagination.

Instructions

Get merge requests for a specific user (as author or assignee) - uses proper GraphQL filtering

Input Schema

NameRequiredDescriptionDefault
roleNoWhether to find MRs authored by or assigned to the userauthor
afterNoPagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals.
firstNoNumber of merge requests to retrieve
stateNoFilter by MR state (opened, closed, merged, all)opened
fetchAllNoFetch multiple pages in one call, up to "first" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor).
usernameYesUsername to find merge requests for (e.g., "cdhanlon")
projectPathNoOptional: limit search to a specific project
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)

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. Changed2 schema fields changedv2.2.4
    • changedInput schema / properties / after / description
      Previous value: -"Cursor for pagination"New value: +"Pagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals."
    • changedInput schema / properties / fetchAll / description
      Previous value: -"Fetch all pages up to 100 results"New value: +"Fetch multiple pages in one call, up to \"first\" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor)."
  3. Changed3 schema fields changedv1.15.0
    • addedInput schema / properties / fetchAll
      Added value: +{
+  "default": false,
+  "description": "Fetch all pages up to 100 results",
+  "type": "boolean"
+}
    • changedInput schema / properties / first / default
      Previous value: -50New value: +20
    • changedInput schema / properties / userCredentials / description
      Previous value: -"Your GitLab credentials (optional - uses shared token if not provided)"New value: +"Your GitLab credentials (optional — falls back to the configured env token if not provided)"
  4. First observedv1.7.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds nothing behavioral beyond that — no note about the default 'opened' state, default page size, or the fact that `fetchAll` is not exhaustive; that critical caveat lives only in the schema. 'Uses proper GraphQL filtering' is unexplained filler.

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

Conciseness3/5

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

It is a single short sentence and front-loads the resource, which is good. But the dangling '- uses proper GraphQL filtering' does not earn its place; it neither guides selection nor explains behavior.

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 read-only, fully-documented listing tool with no output schema, the description plus schema give an agent enough to call it correctly — pagination, defaults and limits all live in the schema. The only real gap is the absence of sibling routing guidance against `get_merge_requests`.

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 eight parameters including the pagination cursor and fetchAll caveat are documented in the schema. The description only restates the author/assignee duality already captured by the `role` enum, adding no syntax or format detail on top.

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?

States a specific verb and resource with its defining scope: merge requests for a specific user, either as author or assignee. That clearly separates it from the general `get_merge_requests` sibling, though the description never names that sibling to make the contrast explicit.

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?

There is no statement of when to prefer this over `get_merge_requests` or `search_merge_requests`, and no exclusions or prerequisites. The trailing clause 'uses proper GraphQL filtering' hints at a reliability advantage but never explains what it means for the caller.

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