gitlab-mcp

List Group Milestones

gitlab_list_group_milestones

Read-onlyIdempotent

List GitLab group milestones and filter them by state, title, search, dates, or ancestor/descendant groups to find relevant milestones quickly.

Instructions

List milestones defined on a group. Supports iids, state, title, search, ancestor/descendant inclusion, and date filters.

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>"
    },
    "name": "gitlab_list_group_milestones"
  }
}

Input Schema

Name	Required	Description	Default
`iids`	No
`page`	No
`state`	No
`title`	No
`search`	No
`end_date`	No
`group_id`	Yes
`per_page`	No
`start_date`	No
`search_title`	No
`updated_after`	No
`updated_before`	No
`containing_date`	No
`include_ancestors`	No
`include_descendants`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds one genuinely useful behavioral note — that results can include ancestors/descendants — but says nothing about pagination, ordering, or the fact that filtering is optional beyond group_id.

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?

Two tight sentences with the resource and scope front-loaded and zero filler. The second sentence is essentially a parameter inventory, which is compact but reads more like a feature list than guidance.

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 listing tool whose annotations and input schema are rich (16 properties, 1 required) and with no output schema, the description covers what the tool does and its main filter surface. The residual gaps — pagination parameters and date format expectations — are modest but real.

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 0%, so the description has to carry parameter meaning, and it does partially by enumerating iids, state, title, search, ancestor/descendant flags, and date filters. However, it merely lists parameter names without format, matching behavior, or interaction rules, and it omits page, per_page, and search_title, leaving several of the 15 parameters undocumented everywhere.

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 uses a specific verb and resource ('List milestones defined on a group') and scopes it to group-level milestones, which implicitly separates it from the project-level sibling gitlab_list_milestones. It stops short of explicitly naming that sibling, so differentiation is inferred rather than stated.

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 group scoping hints at when to prefer this over the project-level list tool, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no pointer to gitlab_get_group_milestone or gitlab_create_group_milestone for the adjacent operations.

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

Deploy Server