Skip to main content
Glama

update_group_milestone

Modify an existing milestone in a GitLab group by updating its title, description, dates, or state to track project progress and deadlines.

Instructions

Update an existing milestone in a GitLab group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup ID or URL-encoded path
milestone_idYesThe ID of the group milestone
titleNoThe title of the milestone
descriptionNoThe description of the milestone
due_dateNoThe due date of the milestone (YYYY-MM-DD)
start_dateNoThe start date of the milestone (YYYY-MM-DD)
state_eventNoThe state event of the milestone

Implementation Reference

  • The actual implementation of the update_group_milestone tool logic using gitlabPut.
    export async function updateGroupMilestone(
      groupId: string,
      milestoneId: number,
      options: {
        title?: string;
        description?: string;
        due_date?: string;
        start_date?: string;
        state_event?: "close" | "activate";
      }
    ): Promise<GitLabGroupMilestoneResponse> {
      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}`;
    
      const milestone = await gitlabPut<GitLabGroupMilestoneResponse>(endpoint, options);
      return GitLabGroupMilestoneSchema.parse(milestone);
    }
  • Zod schema defining the input parameters for the update_group_milestone tool.
    export const UpdateGroupMilestoneSchema = z.object({
      group_id: z.string().describe("Group ID or URL-encoded path"),
      milestone_id: z.number().describe("The ID of the group milestone"),
      title: z.string().optional().describe("The title of the milestone"),
      description: z.string().optional().describe("The description of the milestone"),
      due_date: z.string().optional().describe("The due date of the milestone (YYYY-MM-DD)"),
      start_date: z.string().optional().describe("The start date of the milestone (YYYY-MM-DD)"),
      state_event: z.enum(["close", "activate"]).optional().describe("The state event of the milestone")
    });
  • src/server.ts:377-382 (registration)
    Registration and request handling for the update_group_milestone tool in the MCP server.
    case "update_group_milestone": {
      const args = UpdateGroupMilestoneSchema.parse(request.params.arguments);
      const { group_id, milestone_id, ...options } = args;
      const milestone = await api.updateGroupMilestone(group_id, milestone_id, options);
      return { content: [{ type: "text", text: JSON.stringify(milestone, null, 2) }] };
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is an update operation, implying mutation, but doesn't describe what happens on success/failure, whether changes are reversible, authentication requirements, rate limits, or error conditions. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 front-loads the essential information ('Update an existing milestone in a GitLab group'). There's no wasted verbiage or redundancy, making it easy to parse quickly.

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?

Given this is a mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects (permissions, side effects), usage context versus siblings, or what the tool returns. The high schema coverage helps, but the description alone is insufficient for safe and effective use.

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 schema already documents all 7 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema (e.g., it doesn't explain relationships between parameters like how 'state_event' interacts with other fields). The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Update') and resource ('an existing milestone in a GitLab group'), making the purpose immediately understandable. It distinguishes this from creation tools like 'create_group_milestone' by specifying 'existing', but doesn't explicitly differentiate it from similar update tools like 'update_milestone' (which appears to be for project-level milestones).

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 edit permissions), when not to use it, or how it differs from sibling tools like 'update_milestone' (likely for project milestones) or 'update_issue' (for different resources). Usage is implied but not explicitly defined.

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