gitlab-mcp

List Group Milestone Merge Requests

gitlab_list_group_milestone_merge_requests

Read-onlyIdempotent

List merge requests assigned to a group milestone across the group's projects to review milestone work in one place.

Instructions

List merge requests assigned to a group milestone across the group's projects.

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": {
      "group_id": "<group_id>",
      "milestone_id": "<milestone_id>"
    },
    "name": "gitlab_list_group_milestone_merge_requests"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No
`group_id`	Yes
`per_page`	No
`milestone_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds one genuinely useful behavioral fact — that results span all of the group's projects — but says nothing about pagination, ordering, or result size limits despite exposing page/per_page parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence with the scope front-loaded and no wasted words. It is efficient, though the brevity is part of why parameter and pagination semantics are missing.

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?

Annotations cover the read-only safety profile and there is no output schema to explain, so the core need is minimal. However, with 0% schema coverage the description should at least explain pagination and ID expectations for a 4-parameter list tool, and it does not.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden. It only indirectly indicates what group_id and milestone_id mean ("group milestone", "group's projects") and gives no format guidance, while page and per_page are never mentioned at all — half the parameters remain unexplained.

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?

States a specific verb (List) and resource (merge requests) plus a precise scope: assigned to a group milestone, aggregated across the group's projects. That scope wording implicitly separates it from a plain group merge-request listing or a project-level milestone lookup, but no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The scope phrase implies when the tool applies (you have a group-level milestone ID and want its associated MRs), but there is no explicit when-to-use/when-not guidance and no alternative tool is named for the adjacent cases (e.g. group-wide MR listing or project milestone MRs).

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

Deploy Server