gitlab-mcp

Delete Group Milestone

gitlab_delete_group_milestone

Destructive

Permanently delete a GitLab group milestone, removing it from all issues and merge requests; this action is irreversible. Provide group_id and milestone_id, and verify the milestone first.

Instructions

Delete a group milestone permanently; issues and merge requests lose the milestone. Irreversible. Requires group_id and milestone_id. Recommended pre-check: gitlab_get_group_milestone.

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_delete_group_milestone"
  }
}

Input Schema

Name	Required	Description	Default
`group_id`	Yes
`milestone_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is partly covered. The description still adds real value beyond them: it discloses the cascade effect (issues and merge requests lose the milestone) and states the action is irreversible, which the annotations alone do not convey. Missing is any mention of required permission level or scope.

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?

Two short sentences plus a required-parameter clause, all front-loaded with the action and its consequence. Nothing is padded; "permanently" and "Irreversible" reinforce rather than waste.

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 destructive two-parameter mutation with no output schema, the definition covers consequence, irreversibility, and a safe pre-check path. The remaining gap is operational detail such as permission requirements or error behavior on a nonexistent milestone, which keeps it short of a 5.

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 carries the burden, but it only restates that group_id and milestone_id are required without adding format, source, or lookup meaning. Both parameters are simple string IDs, so the risk of mis-invocation is low, but no new semantic detail is supplied.

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 opens with a specific verb and resource ("Delete a group milestone") and immediately scopes it to group-level milestones, which is the key distinction from the sibling gitlab_delete_milestone. An agent can identify the operation and its target without opening the schema.

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

Usage Guidelines4/5

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

It gives an explicit, actionable pre-check ("Recommended pre-check: gitlab_get_group_milestone"), naming the sibling tool to inspect before deleting. It does not state when-not to use it or contrast against gitlab_delete_milestone, but the destructive nature makes the intent clear.

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

Deploy Server