Skip to main content
Glama
ttpears

GitLab MCP Server

by ttpears

User Merge Requests

get_user_merge_requests
Read-onlyIdempotent

Find merge requests authored by or assigned to a user. Filter by state, project, and paginate to get complete results from GitLab.

Instructions

Get merge requests for a specific user (as author or assignee) - uses proper GraphQL filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
roleNoWhether to find MRs authored by or assigned to the userauthor
afterNoPagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals.
firstNoNumber of merge requests to retrieve
stateNoFilter by MR state (opened, closed, merged, all)opened
fetchAllNoFetch multiple pages in one call, up to "first" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor).
usernameYesUsername to find merge requests for (e.g., "cdhanlon")
projectPathNoOptional: limit search to a specific project
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)
Behavior4/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds useful details about GraphQL filtering and pagination behavior (fetchAll vs cursor), providing context beyond annotations.

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?

The description is a single, clear sentence front-loaded with the core purpose. No unnecessary words.

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?

Although the description is brief, the parameter descriptions are detailed. Lacking output schema, the description could provide more on return structure, but overall it is adequate for an agent to understand the tool's functionality.

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 baseline is 3. The tool description adds little beyond the schema's parameter descriptions; it only reiterates the role parameter's usage in the overall purpose.

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 gets merge requests for a specific user, with role filtering (as author or assignee) and mentions proper GraphQL filtering. This distinguishes it from siblings like get_merge_requests (general) and search_merge_requests.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool vs alternatives such as get_merge_requests or search_merge_requests. The usage is implied by the name and description, but lacking when-not scenarios.

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

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