Skip to main content
Glama
Sign In
gitlab mcp

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_merge_request

Read-only

Retrieve merge request details by IID or source branch, with optional deployment, commit, and approval summaries for review and tracking.

Instructions

Get details of a merge request (merge_request_iid or source_branch required). Set include_summaries=true for deployment/commit/approval summaries. To find resources, use the matching list or search tool.

Input Schema

NameRequiredDescriptionDefault
jmespathNoOptional JMESPath expression filtering the JSON result before return.
project_idYesProject ID or URL-encoded path
source_branchNoSource branch name
include_summariesNoIf true, include deployment, commit, and approval summaries (extra API calls). Default false.
merge_request_iidNoMerge request IID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.3.22
    • changedInput schema / properties / include_summaries / description
      Previous value: -"If true, include deployment_summary, commit_addition_summary and approval_summary (extra API calls, larger response). Default false to reduce token usage."New value: +"If true, include deployment, commit, and approval summaries (extra API calls). Default false."
    • changedInput schema / properties / merge_request_iid / description
      Previous value: -"The IID of a merge request"New value: +"Merge request IID"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID or complete URL-encoded path to project"New value: +"Project ID or URL-encoded path"
  2. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  3. Changed1 schema field changedv2.1.30
    • addedInput schema / properties / include_summaries
      Added value: +{
+  "description": "If true, include deployment_summary, commit_addition_summary and approval_summary (extra API calls, larger response). Default false to reduce token usage.",
+  "type": "boolean"
+}
  4. Addedv2.1.18
  5. Removedv2.1.14
  6. Addedv2.1.11
  7. Removedv2.1.10
  8. Changed2 schema fields changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / required
      Added value: +[
+  "project_id"
+]
  9. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: the identifier requirement that the schema does not enforce (only project_id is required) and the fact that include_summaries triggers extra API calls, which signals added latency/cost. It does not cover failure behavior when neither identifier is supplied, but the value added beyond annotations is real.

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?

Three short sentences, front-loaded with purpose, then the identifier constraint, then the optional flag and the discovery alternative. Every sentence carries distinct information with no repetition of the schema or annotations.

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?

For a read-only fetch tool with a fully documented 5-parameter schema and no output schema, the description covers purpose, required identifiers, and the cost of summaries. The main remaining gap is that it never sketches what 'details' includes (fields, size of payload) or how the jmespath filter interacts with the result, which matters somewhat given no output 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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by stating the cross-parameter constraint (one of merge_request_iid or source_branch must be provided) that the schema's required list does not capture. It also clarifies the practical effect of include_summaries as extra API calls, beyond the schema's 'extra API calls' phrasing. This is meaningful semantics beyond the structured fields.

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 opens with a specific verb and resource ('Get details of a merge request'), which clearly separates it from list_merge_requests and the diff/note/discussion siblings. It does not name a specific sibling it competes with, instead referring generically to 'the matching list or search tool', so it falls short of full sibling differentiation.

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?

It gives clear usage conditions: an identifier (merge_request_iid or source_branch) is required, and include_summaries=true should be set when deployment/commit/approval summaries are wanted. It also routes agents to the list/search tools for discovery. There is no explicit when-not guidance, but the context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools