Skip to main content
Glama
Sign In
gitlab mcp

gitlab mcp

by zereight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_merge_request_notes

Read-only

List flat notes on a merge request for paginated review; use mr_discussions when thread structure or resolution state is needed.

Instructions

List notes for a merge request. List flat notes. Use mr_discussions when thread structure and resolution state are required.

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_id": "<project_id>",
      "merge_request_iid": "<merge_request_iid>"
    },
    "name": "get_merge_request_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination
sortNoThe sort order of the notes
jmespathNoOptional JMESPath expression filtering the JSON result before return.
order_byNoThe field to sort the notes by
per_pageNoNumber of items per page
project_idYesProject ID or complete URL-encoded path to project
merge_request_iidYesThe IID of a merge request

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.66
    • addedInput schema / properties / jmespath
      Added value: +{
+  "description": "Optional JMESPath expression filtering the JSON result before return.",
+  "type": "string"
+}
  2. Addedv2.1.18
  3. Removedv2.1.14
  4. Addedv2.1.11
  5. Removedv2.1.10
  6. Changed4 schema fields changedv2.1.9
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page
      Added value: +{
+  "description": "Page number for pagination",
+  "type": "number"
+}
    • addedInput schema / properties / per_page
      Added value: +{
+  "description": "Number of items per page",
+  "type": "number"
+}
    • addedInput schema / required
      Added value: +[
+  "project_id",
+  "merge_request_iid"
+]
  7. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, open-world operation. The description adds relevant behavioral context by clarifying that returned notes are flat rather than threaded, but it does not mention pagination behavior or any practical limits.

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 short sentences, with the core purpose and the key exclusion front-loaded. There is no redundant or wasted language.

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 list tool with a fully documented schema and annotations, the description is nearly complete. The only minor gap is that it does not describe the return shape or pagination expectations, though the flat-note distinction gives useful context.

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 the input schema already explains all seven parameters. The description adds no parameter-level details beyond the operation itself, which is appropriate baseline behavior when the schema carries the burden.

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 names a specific operation and resource: listing notes for a merge request. It further distinguishes the result as flat notes and explicitly names the sibling tool to use when thread structure is needed.

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?

It gives an explicit alternative: use `mr_discussions` when thread structure and resolution state are required. This directly tells the agent when to choose this tool versus a closely related sibling.

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