Skip to main content
Glama

gitlab_get_merge_request

Read-onlyIdempotent

Get complete details of a GitLab merge request by its IID: state, branches, author, assignees, reviewers, labels, conflict status, description, and timestamps.

Instructions

Get full information about a merge request by internal ID (iid).

Includes state, branches, author, assignees, reviewers, labels, conflict status, description and timestamps.

Examples: - "Show me the description and state of !42" → mr_iid=42 - Don't use to see changed files — use gitlab_get_merge_request_changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mr_iidYesMerge request IID (project-local number shown as '!42').
project_pathNoGitLab project path (e.g. 'my-org/my-repo'). When omitted, the default from GITLAB_PROJECT_PATH env var is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
iidYes
titleYes
descriptionYes
stateYes
source_branchYes
target_branchYes
authorYes
assigneesYes
reviewersYes
labelsYes
merge_statusYes
has_conflictsYes
changes_countYes
created_atYes
updated_atYes
merged_atYes
web_urlYes
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds context about returned fields (state, branches, etc.) and no side effects are mentioned, reinforcing safe read behavior.

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?

Six concise lines with front-loaded purpose, clear structure, and no superfluous text. Every sentence earns its place.

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

Completeness5/5

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

Given robust annotations, full schema coverage, and presence of output schema, the description provides all necessary context: purpose, scope, usage guidance, and differentiation from siblings.

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?

Schema coverage is 100% with good descriptions, but the description adds value by giving usage context (e.g., example showing mr_iid=42, note about project_path default) beyond the schema.

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?

Description clearly states it gets full information about a merge request by internal ID (iid) and lists included details. It distinguishes from sibling gitlab_get_merge_request_changes by explicitly saying not to use for changed files.

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 examples of when to use (e.g., 'Show me the description and state of !42') and directs away from use for changed files, naming the alternative tool.

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

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