Skip to main content
Glama
Sign In
@wanadev/mcp-gitlab

@wanadev/mcp-gitlab

by wanadev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_project_milestones

Read-only

Retrieve project milestones filtered by state or title. Lists milestones scoped to a project in GitLab.

Instructions

List milestones at the project level. On GitLab CE/Free, milestones are project-scoped and this is the only way to list them.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID
stateNoFilter by state
searchNoSearch by title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=true, which is consistent. The description adds context about project-scoping and edition-specific behavior, but does not disclose default behavior (e.g., whether all milestones are returned by default) or address pagination or sorting.

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 two sentences long, no unnecessary words, and directly addresses the tool's purpose. Every sentence adds value.

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 simple nature of the tool (3 params, no output schema), the description covers the core purpose and scope. However, it lacks details on pagination, result order, or any limitations, leaving some gaps for an AI agent.

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?

The input schema has 100% description coverage for all three parameters, so the schema already explains them. The description adds no new parameter details, so baseline score of 3 is appropriate.

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 verb "list" and the resource "milestones at the project level." It adds context about GitLab CE/Free, distinguishing it from potentially similar sibling tools like "list_milestones" which may be group-level.

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 description implies usage by stating it is the only way to list milestones in GitLab CE/Free, but it does not explicitly mention when to use it over alternatives like list_milestones or when not to use it. The guidance is implicit rather than explicit.

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