GitLab MCP Server

get_merge_request_comments

Retrieves comments and notes from a specific merge request. Provide the project path and merge request IID to access discussions and feedback.

Instructions

Get comments/notes on a specific merge request.

Args: project_path: Full path of the project (e.g., 'group/project') mr_iid: The internal ID of the merge request within the project per_page: Number of results per page (max 100)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_path": "<project_path>",
      "mr_iid": "<mr_iid>"
    },
    "name": "get_merge_request_comments"
  }
}

Input Schema

Name	Required	Description	Default
`mr_iid`	Yes
`per_page`	No
`project_path`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 6, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without disclosing important behaviors such as pagination limits (beyond per_page parameter), error handling, ordering, or response structure. This is insufficient for an agent to fully understand tool 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?

The description is extremely concise: one sentence for purpose followed by a bullet list of parameter descriptions. Every sentence is necessary and adds value. The purpose is front-loaded, making it easy to understand at a glance.

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

Completeness3/5

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

Given the tool's low complexity and the presence of an output schema, the description is adequate but minimally complete. It covers the main action and parameters but lacks details on pagination behavior beyond the per_page parameter, default sorting, or what happens when no comments exist. More context would improve completeness.

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?

The description provides meaningful explanations for all three parameters, including example values ('group/project') and constraints ('max 100'). This adds significant value beyond the input schema, which has 0% schema description coverage. The explanations are clear and helpful.

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 retrieves comments/notes on a specific merge request. It uses a specific verb 'Get' and resource 'comments/notes', and distinguishes itself from siblings like 'get_merge_request' (which gets the MR itself) and 'get_issue_comments' (which targets issues).

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It only states what it does, leaving the agent to infer usage context. No 'when not to use' or references to sibling tools are given.

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