Skip to main content
Glama

list_merge_requests

Read-only

Retrieve merge requests from GitLab, scoped to a project or across all accessible projects, with optional filters for state, labels, author, assignee, and search terms.

Instructions

List merge requests (without project_id: user's MRs; with project_id: project MRs). Use this for a collection of resources; choose the corresponding get tool when you already know the single resource to inspect. It is read-only and does not mutate GitLab data; missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors. When project_id or group_id is accepted, provide the numeric ID or complete URL-encoded path described by the schema; use required identifiers and pagination fields exactly as documented.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wipNoFilter merge requests against their wip status
pageNoPage number for pagination (default: 1)
sortNoReturn merge requests sorted in ascending or descending order
scopeNoReturn merge requests from a specific scope
stateNoReturn merge requests with a specific state
labelsNoArray of label names
searchNoSearch for specific terms
order_byNoReturn merge requests ordered by the given field
per_pageNoNumber of items per page (max: 100, default: 20)
author_idNoReturns merge requests created by the given user ID (integer). Mutually exclusive with author_username.
milestoneNoMilestone title
project_idNoProject ID or URL-encoded path (optional - if not provided, lists all merge requests the user has access to)
assignee_idNoReturn MRs assigned to the given user ID (integer), 'none', or 'any'. Mutually exclusive with assignee_username.
reviewer_idNoReturns merge requests which have the user as a reviewer. Must be an integer, 'none', or 'any'. Mutually exclusive with reviewer_username.
created_afterNoReturn merge requests created after the given time
source_branchNoReturn merge requests from a specific source branch
target_branchNoReturn merge requests targeting a specific branch
updated_afterNoReturn merge requests updated after the given time
created_beforeNoReturn merge requests created before the given time
updated_beforeNoReturn merge requests updated before the given time
author_usernameNoReturns merge requests created by the given username. Mutually exclusive with author_id.
assignee_usernameNoReturns merge requests assigned to the given username. Mutually exclusive with assignee_id.
reviewer_usernameNoReturns merge requests which have the user as a reviewer by username. Mutually exclusive with reviewer_id.
with_labels_detailsNoReturn more details for each label
approved_by_usernamesNoReturns merge requests approved by the given usernames (array).

Schema Changelog

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

  1. Addedv2.1.18
  2. Removedv2.1.14
  3. Addedv2.1.11
  4. Removedv2.1.10
  5. Changed8 schema fields changedv2.1.9
    • 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."
  6. First observedv1.0.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=true and openWorldHint=true, so the read-only nature is known. The description adds value by listing error conditions (missing resources, invalid identifiers, insufficient permission, rate limits) and clarifying the scoping behavior (user vs project MRs). It doesn't contradict any annotation, but it restates the read-only aspect partially.

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, no fluff. The primary purpose and scoping is front-loaded, then usage guidance and error handling are packed in a second sentence. Every clause adds information; nothing is redundant.

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?

Given the tool has 25 parameters and no output schema, the description provides the essential usage context (collection vs single), error behavior, and parameter format guidance. It doesn't need to enumerate every parameter since schema covers them. The only minor gap is not explaining the return format, but for a list tool this is typically obvious and not critical.

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 every parameter already has a description. The tool description adds a high-level note about using identifiers and pagination exactly as documented, but doesn't deep-dive into specific parameters. With full schema coverage, the baseline is 3, and the description's added value is minimal.

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 clearly states the verb 'List' and the resource 'merge requests', then explicitly distinguishes the two modes (user-level vs project-level) based on presence of project_id. It also names the sibling get tool and when to use it, making it unambiguous which tool to pick.

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?

It explicitly says to use this for a collection and to choose the corresponding get tool for a single known resource. It also gives error-handling guidance (missing resources, invalid IDs, permission, rate limits) and instructs on ID formats (numeric or URL-encoded path) and pagination parameters. This is precise, actionable direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zereight/gitlab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server