Skip to main content
Glama
ttpears

GitLab MCP Server

by ttpears

Milestones

list_milestones
Read-onlyIdempotent

List milestones for a project or group and get progress statistics including total and closed issue counts.

Instructions

List milestones for a project or group with progress statistics (total/closed issue counts)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoPagination cursor. To fetch the next page, pass the previous response pageInfo.endCursor here and repeat until pageInfo.hasNextPage is false. Paginating this way is the reliable path to complete results and accurate totals.
firstNoNumber of milestones to retrieve
stateNoFilter by state: active, closed (omit for all)
searchNoSearch milestones by title
fetchAllNoFetch multiple pages in one call, up to "first" items total (max 100) — NOT exhaustive. For complete results or accurate counts, leave this false and paginate via after (pageInfo.endCursor).
fullPathYesFull path of the project or group (e.g., "group/project-name" or "group")
isProjectYesWhether the path is a project (true) or group (false)
userCredentialsNoYour GitLab credentials (optional — falls back to the configured env token if not provided)
includeAncestorsNoInclude milestones from ancestor groups
Behavior4/5

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

The description adds value beyond annotations by stating that the tool returns progress statistics (total/closed issue counts). It is consistent with readOnlyHint and idempotentHint, and does not contradict annotations.

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 a single sentence of 12 words, extremely concise and front-loaded with the essential purpose. Every word earns its place.

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 has 9 parameters and no output schema, the description is minimal. It does not mention pagination, iteration, or the required identifiers. However, the schema descriptions are complete, so the agent can infer details from there.

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 baseline is 3. The description does not add new information about parameters beyond what the schema already provides.

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 specifies the verb (List), resource (milestones), and context (for a project or group) with a unique feature (progress statistics with total/closed issue counts). This differentiates it from sibling tools like list_iterations or list_work_items.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., list_iterations, get_issues). The description does not mention exclusions or prerequisites like requiring fullPath and isProject, which are required parameters.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ttpears/gitlab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server