Skip to main content
Glama
Sign In
GitLab MCP Server

GitLab MCP Server

by ttpears
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Review Bottlenecks

analytics_review_bottlenecks
Read-onlyIdempotent

Aggregate open non-draft merge requests across a group or project to surface review bottlenecks, showing per-reviewer queues, age buckets, and stalest MRs.

Instructions

Aggregate open (non-draft) merge requests across a group or project to surface review bottlenecks. Returns per-reviewer queue stats, age-bucket histogram, and the stalest MRs by updatedAt. MRs with no reviewer assigned are bucketed under "(unassigned)".

Input Schema

NameRequiredDescriptionDefault
groupNoGroup full path (e.g. "my-group"). Mutually exclusive with `project`.
maxMRsNoHard cap on MRs scanned. Envelope flags `truncated:true` if reached.
projectNoProject full path (e.g. "my-group/my-project"). Mutually exclusive with `group`.
topStalestNoCap on the stalest[] list. Default 20.
staleAfterDaysNoAn MR counts as "stale" if its updatedAt is older than this many days. Default 3.
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / staleAfterDays / maximum
      Added value: +9007199254740991
    • 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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond annotations: it only considers open non-draft MRs, returns per-reviewer queues, an age histogram, stalest MRs by updatedAt, and buckets unassigned MRs under '(unassigned)'.

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 three tight sentences with no filler. The core action and output shape are front-loaded before the unassigned-bucket detail.

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?

There is no output schema, but the description adequately explains the return shape: per-reviewer queue stats, age-bucket histogram, and stalest MRs. It does not clarify the behavior if neither group nor project is supplied, despite zero required parameters, which is a minor remaining gap.

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 six parameters are already documented in the input schema. The description mentions group/project aggregation and the stalest output, but does not add parameter-level meaning beyond the schema's own mutual-exclusivity, defaults, and truncation notes.

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?

The description states a specific verb and resource: aggregate open (non-draft) merge requests across a group or project to surface review bottlenecks. It also names the exact output categories, making it clearly distinguishable from simple MR-listing siblings like get_merge_requests.

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?

The phrase 'to surface review bottlenecks' gives clear context for when to use this tool rather than raw MR retrieval. However, it does not explicitly exclude alternatives or name sibling analytics tools such as analytics_user_summary or analytics_group_summary.

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