gitlab mcp

list_merge_requests

Read-only

List GitLab merge requests for a user or project, with filters for state, labels, author, assignee, reviewer, branch, and dates. Use it to review open, merged, or closed MRs.

Instructions

List merge requests (without project_id: user's MRs; with project_id: project MRs). For one known resource, use the matching get tool. Read-only; missing resources, denied access, and rate limits return errors. project_id/group_id take a numeric ID or URL-encoded path.

Input Schema

TableJSON Schema

Name	Required	Description
`wip`	No	Filter merge requests against their wip status
`page`	No	Page number for pagination (default: 1)
`sort`	No	Return merge requests sorted in ascending or descending order
`scope`	No	Return merge requests from a specific scope
`state`	No	Return merge requests with a specific state
`labels`	No	Array of label names
`search`	No	Search for specific terms
`jmespath`	No	Optional JMESPath expression filtering the JSON result before return.
`order_by`	No	Return merge requests ordered by the given field
`per_page`	No	Number of items per page (max: 100, default: 20)
`author_id`	No	Returns merge requests created by the given user ID (integer). Mutually exclusive with author_username.
`milestone`	No	Milestone title
`project_id`	No	Project ID or URL-encoded path (optional - if not provided, lists all merge requests the user has access to)
`assignee_id`	No	Return MRs assigned to the given user ID (integer), 'none', or 'any'. Mutually exclusive with assignee_username.
`reviewer_id`	No	Returns merge requests which have the user as a reviewer. Must be an integer, 'none', or 'any'. Mutually exclusive with reviewer_username.
`created_after`	No	Return merge requests created after the given time
`source_branch`	No	Return merge requests from a specific source branch
`target_branch`	No	Return merge requests targeting a specific branch
`updated_after`	No	Return merge requests updated after the given time
`created_before`	No	Return merge requests created before the given time
`updated_before`	No	Return merge requests updated before the given time
`author_username`	No	Returns merge requests created by the given username. Mutually exclusive with author_id.
`assignee_username`	No	Returns merge requests assigned to the given username. Mutually exclusive with assignee_id.
`reviewer_username`	No	Returns merge requests which have the user as a reviewer by username. Mutually exclusive with reviewer_id.
`with_labels_details`	No	Return more details for each label
`approved_by_usernames`	No	Returns merge requests approved by the given usernames (array).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.1.66Sep 23, 2026

addedInput schema / properties / jmespath

Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}

Addedv2.1.18May 30, 2026
Removedv2.1.14May 22, 2026
Addedv2.1.11May 13, 2026
Removedv2.1.10May 9, 2026

Changed8 schema fields changedv2.1.9May 9, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / assignee_id / description

Previous value: -"Return issues assigned to the given user ID. user id or none or any"New value: +"Return MRs assigned to the given user ID (integer), 'none', or 'any'. Mutually exclusive with assignee_username."

changedInput schema / properties / assignee_username / description

Previous value: -"Returns merge requests assigned to the given username"New value: +"Returns merge requests assigned to the given username. Mutually exclusive with assignee_id."

changedInput schema / properties / author_id / description

Previous value: -"Returns merge requests created by the given user ID"New value: +"Returns merge requests created by the given user ID (integer). Mutually exclusive with author_username."

changedInput schema / properties / author_username / description

Previous value: -"Returns merge requests created by the given username"New value: +"Returns merge requests created by the given username. Mutually exclusive with author_id."

changedInput schema / properties / project_id / description

Previous value: -"Project ID or URL-encoded path"New value: +"Project ID or URL-encoded path (optional - if not provided, lists all merge requests the user has access to)"

changedInput schema / properties / reviewer_id / description

Previous value: -"Returns merge requests which have the user as a reviewer. user id or none or any"New value: +"Returns merge requests which have the user as a reviewer. Must be an integer, 'none', or 'any'. Mutually exclusive with reviewer_username."

changedInput schema / properties / reviewer_username / description

Previous value: -"Returns merge requests which have the user as a reviewer"New value: +"Returns merge requests which have the user as a reviewer by username. Mutually exclusive with reviewer_id."

First observedv1.0.0Jan 2, 2026

TDQS

A4.2/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 real behavioral context beyond that: missing resources, denied access, and rate limits all surface as errors, which an agent needs to anticipate.

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?

Four tight sentences, each load-bearing: scope semantics, sibling routing, error behavior, and parameter format. The most decision-relevant fact (scope of project_id) is front-loaded.

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 26-param read tool with no output schema, the description covers scope, the get/list boundary, error conditions, and ID formatting. An agent can call it correctly; pagination behavior (page/per_page defaults) is left to the schema, which is acceptable.

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 26 parameters are already documented. The description's note that project_id/group_id accept a numeric ID or URL-encoded path largely repeats the schema's own wording, so it adds only marginal value; baseline 3 applies.

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 verb (List) and resource (merge requests) and then disambiguates scope: without project_id it returns the user's MRs, with project_id it returns project MRs. It also explicitly routes single-resource lookups to the matching get tool, distinguishing it from get_merge_request.

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?

Gives clear context for the two modes and points to the alternative ('use the matching get tool') when a single known resource is needed. It stops short of naming get_merge_request explicitly or describing when to prefer other list siblings like list_merge_request_diffs.

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

list_merge_requests

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools