Skip to main content
Glama

list_merge_requests

Read-only

List merge requests from GitLab, optionally filtered by project, assignee, author, reviewer, labels, state, or search terms.

Instructions

List merge requests (without project_id: user's MRs; with project_id: project MRs)

Input Schema

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

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description only states basic listing behavior without additional traits like pagination limits or response structure, which is adequate but not enhanced.

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?

One sentence that is perfectly front-loaded with the key information. No redundant words; every part adds value.

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?

With 25 parameters and no output schema, the description is minimal. It omits details about pagination, default sorting, or return fields, relying heavily on the schema. Adequate but not fully complete for a complex list tool.

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% (all 25 parameters described). The tool description adds only the project_id distinction, so it meets the baseline 3 but does not exceed it.

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 tool lists merge requests and distinguishes between user-level and project-level based on project_id. This differentiates it from sibling tools like 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?

Provides explicit guidance on when to include project_id (user's MRs vs project MRs). Does not explicitly contrast with other list tools, but the behavior is self-evident.

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