Skip to main content
Glama

delete_group_milestone

Remove a milestone from a GitLab group to clean up project tracking and organize development workflows.

Instructions

Delete a milestone from a GitLab group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup ID or URL-encoded path
milestone_idYesThe ID of the group milestone

Implementation Reference

  • Handler for the delete_group_milestone tool, implementing the API call to delete a milestone from a group.
    export async function deleteGroupMilestone(groupId: string, milestoneId: number): Promise<void> {
      if (!groupId?.trim()) {
        throw new Error("Group ID is required");
      }
      if (!milestoneId || milestoneId < 1) {
        throw new Error("Valid milestone ID is required");
      }
    
      const endpoint = `/groups/${encodeURIComponent(groupId)}/milestones/${milestoneId}`;
      await gitlabDelete(endpoint);
    }
  • Zod schema for validating arguments to the delete_group_milestone tool.
    export const DeleteGroupMilestoneSchema = z.object({
      group_id: z.string().describe("Group ID or URL-encoded path"),
      milestone_id: z.number().describe("The ID of the group milestone")
    });
  • src/server.ts:384-386 (registration)
    Tool registration/invocation logic for delete_group_milestone in the main server handler.
    case "delete_group_milestone": {
      const args = DeleteGroupMilestoneSchema.parse(request.params.arguments);
      await api.deleteGroupMilestone(args.group_id, args.milestone_id);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the destructive action ('Delete') but doesn't mention whether deletion is permanent/reversible, what happens to associated issues/merge requests, rate limits, authentication requirements, or error conditions. This is inadequate for a destructive operation.

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, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately front-loaded with the key action and resource.

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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It doesn't address critical context like permissions needed, side effects, confirmation requirements, or what the tool returns (success/failure indicators). The 100% schema coverage helps with parameters but doesn't compensate for missing behavioral information.

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%, with both parameters clearly documented in the schema. The description doesn't add any additional semantic context about parameters beyond what the schema provides (e.g., format examples, validation rules, or relationship between group_id and milestone_id).

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 clearly states the action ('Delete') and resource ('a milestone from a GitLab group'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'delete_milestone' or 'delete_label', which would require specifying it's for group-level milestones specifically.

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. It doesn't mention prerequisites (e.g., needing admin permissions), when deletion is appropriate versus updating, or how it differs from 'delete_milestone' (which appears to be for project-level milestones based on sibling names).

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/TheRealChrisThomas/gitlab-mcp-server'

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