Skip to main content
Glama

Gitlab

by io.github.pipeworx-io

Gitlab List Mrs

gitlab_list_mrs
Read-onlyIdempotent

List merge requests in a GitLab project by project ID. Returns MR ID, title, state, author, source/target branches, and URL. Filter by state and author.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stateNoFilter by state: "opened", "closed", "merged", or "all" (default: "opened")
_apiKeyYesGitLab personal access token
per_pageNoNumber of merge requests to return (default 20, max 100)
project_idYesProject ID or URL-encoded path

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
merge_requestsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "merge_requests": {
+      "items": {
+        "properties": {
+          "author": {
+            "description": "Author username",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "created_at": {
+            "description": "Creation timestamp",
+            "type": "string"
+          },
+          "iid": {
+            "description": "Merge request internal ID",
+            "type": "number"
+          },
+          "merge_status": {
+            "description": "Merge status",
+            "type": "string"
+          },
+          "source_branch": {
+            "description": "Source branch name",
+            "type": "string"
+          },
+          "state": {
+            "description": "Merge request state (opened/closed/merged)",
+            "type": "string"
+          },
+          "target_branch": {
+            "description": "Target branch name",
+            "type": "string"
+          },
+          "title": {
+            "description": "Merge request title",
+            "type": "string"
+          },
+          "updated_at": {
+            "description": "Last update timestamp",
+            "type": "string"
+          },
+          "url": {
+            "description": "Merge request web URL",
+            "type": "string"
+          }
+        },
+        "required": [
+          "iid",
+          "title",
+          "state",
+          "author",
+          "source_branch",
+          "target_branch",
+          "merge_status",
+          "url",
+          "created_at",
+          "updated_at"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "merge_requests"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-gitlab-api-key",
+    "project_id": "123"
+  },
+  {
+    "_apiKey": "your-gitlab-api-key",
+    "per_page": 50,
+    "project_id": "123",
+    "state": "merged"
+  }
+]
  3. First observed

TDQS

A3.6/5.0
Behavior3/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 that the tool requires a project ID and returns specific fields, but return fields are also in the output schema, so this adds limited value. No hidden behaviors are disclosed, but annotations carry the burden.

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?

The description is only two sentences and front-loads the core purpose, which is structurally concise. However, the inaccuracy about filtering by author means the second sentence does not fully earn its place. A concise, accurate description would score higher.

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

Completeness3/5

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

Given the tool's simplicity, full schema coverage, and output schema existence, the description is mostly adequate. The author filter claim introduces ambiguity and the default state (opened) is not mentioned, though it is in the schema. The description is not fully complete due to the inaccuracy.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. However, the description claims 'Filter by state and author', but the schema does not include an 'author' parameter. This is misleading and could cause an agent to pass an unsupported parameter. The error in the description outweighs the schema's completeness, so a lower score is warranted.

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 uses a specific verb ('List') and identifies the exact resource ('merge requests in a GitLab project by project ID'). It clearly differentiates from sibling tools like gitlab_list_issues and gitlab_list_projects by specifying merge requests and the project scoping. The return fields are also listed, aiding purpose clarity.

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 description provides clear context: use this tool to list merge requests for a given project ID. It does not explicitly mention alternatives or exclusions, but the sibling tools are for different resources (files, projects, issues), so the intended usage is unambiguous. A slightly higher score would require explicit when-not guidance.

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

All Gitlab toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, notably ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded which are near-identical in function. The polymarket_* family also has several members with closely related scopes, and the large number of data-query tools makes it hard to choose the right one without careful reading.

Naming Consistency3/5

All names use snake_case, but the pattern is inconsistent: some are verb-first (list_subscriptions, validate_claim), others are noun-first (entity_profile, bet_research), and proper-noun prefixes like pipeworx_ and polymarket_ are used liberally. The gitlab_* tools follow a clear verb_noun pattern, but the rest of the set is mixed.

Tool Count2/5

With 36 tools, the server is overloaded, especially given that only 5 are GitLab-related while the rest are a sprawling data-access toolkit. Many tools could be consolidated (e.g., the ask_pipeworx variants), and the count exceeds what is reasonable for a focused GitLab server.

Completeness2/5

For a server named Gitlab, the coverage is severely incomplete: only list/get operations exist for projects, issues, and MRs, with no create, update, or delete capabilities. The broader data tools are more complete, but the nominal purpose of the server is clearly not fulfilled.

Resources