Skip to main content
Glama
Alosies

GitLab MCP Server

by Alosies

list_merge_requests

List and filter merge requests in a GitLab project by state, scope, author, assignee, reviewer, and branches.

Instructions

List merge requests in a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoReturn merge requests with the given scope (optional)
stateNoFilter by merge request stateopened
searchNoSearch merge requests by title and description
per_pageNoNumber of results per page (max 100)
author_idNoFilter by author user ID
project_idYesProject ID or path
assignee_idNoFilter by assignee user ID
reviewer_idNoFilter by reviewer user ID
source_branchNoFilter by source branch
target_branchNoFilter by target branch
reviewer_usernameNoFilter by reviewer username
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as pagination, sorting, or performance implications. It is too brief.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but underspecified. It does not earn its place by providing sufficient context.

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

Completeness1/5

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

With 11 parameters and no output schema, the description is far too brief. It lacks information on common use cases, filtering, or pagination.

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 coverage is 100%, so each parameter already has a description. The description adds no additional meaning beyond what is in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'list' and the resource 'merge requests in a project'. It is specific but does not differentiate from sibling tools like 'list_mr_discussions' or 'list_mr_notes'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus other merge request tools or filters. There is no mention of scope or context.

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/Alosies/gitlab-mcp-server'

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