Skip to main content
Glama

update_milestone

Modify milestone details like title, description, due date, or state in a GitLab project to track project progress and deadlines.

Instructions

Update an existing milestone in a GitLab project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
milestone_idYes
titleNo
descriptionNo
due_dateNo
start_dateNo
state_eventNo

Implementation Reference

  • The actual handler implementation for update_milestone, which performs a PUT request to the GitLab API.
    export async function updateMilestone(
      projectId: string,
      milestoneId: number,
      options: {
        title?: string;
        description?: string;
        due_date?: string;
        start_date?: string;
        state_event?: "close" | "activate";
      }
    ): Promise<GitLabMilestoneResponse> {
      if (!projectId?.trim()) {
        throw new Error("Project ID is required");
      }
      if (!milestoneId || milestoneId < 1) {
        throw new Error("Valid milestone ID is required");
      }
    
      const endpoint = `/projects/${encodeProjectId(projectId)}/milestones/${milestoneId}`;
    
      const milestone = await gitlabPut<GitLabMilestoneResponse>(endpoint, options);
      return GitLabMilestoneSchema.parse(milestone);
    }
  • The Zod schema defining the inputs for update_milestone.
    export const UpdateMilestoneSchema = z.object({
      project_id: z.string(),
      milestone_id: z.number(),
      title: z.string().optional(),
      description: z.string().optional(),
      due_date: z.string().optional(),
      start_date: z.string().optional(),
      state_event: z.enum(["close", "activate"]).optional()
    });
  • src/server.ts:344-349 (registration)
    The registration and routing logic for the update_milestone tool in the server request handler.
    case "update_milestone": {
      const args = UpdateMilestoneSchema.parse(request.params.arguments);
      const { project_id, milestone_id, ...options } = args;
      const milestone = await api.updateMilestone(project_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 full burden for behavioral disclosure. It states this is an update operation (implying mutation) but provides no information about permissions required, whether changes are reversible, rate limits, error conditions, or what the response contains. This leaves significant gaps for a mutation tool.

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 with zero wasted words. It's appropriately sized for a basic tool description and front-loads the essential information.

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 mutation tool with 7 parameters, 0% schema description coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain what happens when the tool is invoked, what fields are optional versus required beyond the schema minimum, or what the expected outcome is. Significant context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but provides no parameter information. It doesn't explain what 'project_id' or 'milestone_id' should be, what fields can be updated, or the meaning of parameters like 'state_event' with its enum values. The description adds no value beyond what the bare schema provides.

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 target resource ('an existing milestone in a GitLab project'), which is specific and unambiguous. It distinguishes from sibling tools like 'create_milestone' by specifying 'existing', but doesn't explicitly differentiate from 'update_group_milestone' or other update tools.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing an existing milestone), when not to use it, or how it differs from similar tools like 'update_group_milestone' or 'create_milestone'.

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