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

@wanadev/mcp-gitlab

by wanadev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_project_milestone

Update project milestone details like title, description, dates, or state with a dry-run preview by default. Confirm execution to apply changes.

Instructions

Update a project-level milestone. dry_run=true by default.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID
milestone_idYesMilestone ID
titleNoNew title
descriptionNoNew description (Markdown)
start_dateNoNew start date (YYYY-MM-DD)
due_dateNoNew due date (YYYY-MM-DD)
state_eventNoLifecycle transition
dry_runNoDry run mode (default: true). When true, returns a preview of the action without executing it. Set to false only after user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.8.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already indicate the tool is not read-only (readOnlyHint=false), and the description adds the key detail that `dry_run=true` by default, implying a preview mode. However, it omits what the preview returns and does not elaborate on side effects beyond the schema. The description adds minimal value beyond the annotations and schema.

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 with a second sentence clarifying the default behavior. It is front-loaded with the core purpose and contains no unnecessary words. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite a concise description, it lacks important context: no explanation of return values (no output schema), no prerequisites (project/milestone existence), and no details on partial vs full updates. For a mutation tool with 8 parameters and no output schema, the description is insufficient.

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?

With 100% schema coverage, the input schema fully documents each parameter. The description does not add additional meaning beyond highlighting the `dry_run` default, which is already in the schema. 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 action ('Update') and the resource ('a project-level milestone'), distinguishing it from group-level milestones and other actions like creation or closure. This specificity helps the agent identify the correct tool among siblings.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., `update_milestone` for group milestones, `close_project_milestone` for closing). It also lacks prerequisites or context about required permissions or dependencies.

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