Skip to main content
Glama

create_milestone

Create a new milestone in a GitLab project to track progress, set deadlines, and organize work by specifying project ID, title, description, and dates.

Instructions

Create a new milestone in a GitLab project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYes
titleYes
descriptionNo
due_dateNo
start_dateNo

Implementation Reference

  • The actual implementation of the 'createMilestone' function.
    export async function createMilestone(
      projectId: string,
      title: string,
      description?: string,
      dueDate?: string,
      startDate?: string
    ): Promise<GitLabMilestoneResponse> {
      if (!projectId?.trim()) {
        throw new Error("Project ID is required");
      }
      if (!title?.trim()) {
        throw new Error("Milestone title is required");
      }
    
      const endpoint = `/projects/${encodeProjectId(projectId)}/milestones`;
    
      const milestone = await gitlabPost<GitLabMilestoneResponse>(endpoint, {
        title,
        description,
        due_date: dueDate,
        start_date: startDate
      });
    
      return GitLabMilestoneSchema.parse(milestone);
    }
  • Zod schema for the inputs of create_milestone.
    export const CreateMilestoneSchema = z.object({
      project_id: z.string(),
      title: z.string(),
      description: z.string().optional(),
      due_date: z.string().optional(),
      start_date: z.string().optional()
    });
  • src/server.ts:332-342 (registration)
    Tool handler registration and execution for create_milestone in the server.
    case "create_milestone": {
      const args = CreateMilestoneSchema.parse(request.params.arguments);
      const milestone = await api.createMilestone(
        args.project_id,
        args.title,
        args.description,
        args.due_date,
        args.start_date
      );
      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 a creation operation, implying mutation, but doesn't address permissions required, whether it's idempotent, error conditions, or what happens on success (e.g., returns milestone ID). For a mutation tool with zero annotation coverage, this is insufficient.

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, direct sentence with no wasted words. It's appropriately sized for a basic tool description and front-loads the essential information. Every word 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?

For a mutation tool with 5 parameters, 0% schema coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, or parameter details. Given the complexity and lack of structured data, more context is needed for effective use.

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?

The description provides no information about parameters beyond what's implied by the tool name. With 5 parameters and 0% schema description coverage, the description doesn't compensate by explaining what 'project_id', 'title', 'description', 'due_date', or 'start_date' mean or how they should be formatted. This leaves significant gaps in understanding.

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 ('Create') and resource ('new milestone in a GitLab project'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'create_group_milestone' or other creation tools like 'create_issue' or 'create_label', which would require more specific differentiation.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., project access), when to choose this over 'create_group_milestone', or how it relates to other milestone tools like 'list_milestones' or 'update_milestone'. This leaves the agent without contextual direction.

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