Skip to main content
Glama
ttpears

GitLab MCP Server

by ttpears

Search Merge Requests

search_merge_requests
Read-onlyIdempotent

Search GitLab merge requests by username, author, assignee, or within a project. Filter by state, sort order, and paginate results for comprehensive MR discovery.

Instructions

Search merge requests by username (supports "username", "author:username", "assignee:username") or search within a specific project. Note: GitLab does not support global text search for MRs - use projectPath for text searches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order (e.g., UPDATED_DESC, CREATED_DESC, CREATED_ASC). Defaults to UPDATED_DESC for recency.
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 merge request state (opened, closed, merged, all)all
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).
searchTermYesUsername (e.g., "cdhanlon", "author:username", "assignee:username") or text when projectPath provided
projectPathNoProject path (e.g., "group/project"). Required for text searches, optional for username searches.
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 declare readOnlyHint and idempotentHint true, indicating safe reads. The description adds important behavioral constraints (no global text search, projectPath required for text), going 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?

Two concise sentences that front-load the main functionality and key constraint. No redundant information.

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 8 parameters, no output schema, and annotations covering safety, the description adequately explains the tool's purpose and usage limitations. It lacks details on pagination, but those are described in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All parameters are described in the schema (100% coverage). The description adds value by clarifying searchTerm patterns ('username', 'author:username', etc.) and emphasizing projectPath necessity for text searches.

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 it searches merge requests by username patterns or within a project, distinguishing it from sibling tools like 'get_merge_requests' which likely fetch without search.

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?

Provides explicit when-to-use: username-based search or project-scoped text search. Also includes a key caveat that GitLab does not support global text search, guiding the agent to use projectPath for text searches.

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