Skip to main content
Glama

create_group_milestone

Create milestones in GitLab groups to track project progress, set deadlines, and organize work across multiple projects.

Instructions

Create a new milestone in a GitLab group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup ID or URL-encoded path
titleYesThe 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)

Implementation Reference

  • The actual implementation of the 'create_group_milestone' tool.
    export async function createGroupMilestone(
      groupId: string,
      title: string,
      description?: string,
      dueDate?: string,
      startDate?: string
    ): Promise<GitLabGroupMilestoneResponse> {
      if (!groupId?.trim()) {
        throw new Error("Group ID is required");
      }
      if (!title?.trim()) {
        throw new Error("Milestone title is required");
      }
    
      const endpoint = `/groups/${encodeURIComponent(groupId)}/milestones`;
    
      const milestone = await gitlabPost<GitLabGroupMilestoneResponse>(endpoint, {
        title,
        description,
        due_date: dueDate,
        start_date: startDate
      });
    
      return GitLabGroupMilestoneSchema.parse(milestone);
    }
  • Input schema definition for the create_group_milestone tool.
    export const CreateGroupMilestoneSchema = z.object({
      group_id: z.string().describe("Group ID or URL-encoded path"),
      title: z.string().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)")
    });
  • src/server.ts:365-367 (registration)
    Tool registration and handler invocation in the MCP server.
    case "create_group_milestone": {
      const args = CreateGroupMilestoneSchema.parse(request.params.arguments);
      const milestone = await api.createGroupMilestone(
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the creation action without disclosing behavioral traits like required permissions, whether it's idempotent, error handling, or what happens on success/failure. 'Create' implies mutation but lacks details on side effects or system impact.

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 front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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 no annotations and no output schema, the description is inadequate. It doesn't explain what a 'milestone' represents in GitLab, what happens after creation, or what the tool returns. Given the complexity of creating a resource in a version control system, more context is needed for an agent to use it effectively.

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%, providing clear documentation for all 5 parameters. The description adds no additional parameter semantics beyond implying 'group_id' targets a GitLab group, which is already evident from the schema. Baseline 3 is appropriate when 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 ('Create a new milestone') and target resource ('in a GitLab group'), which is specific and unambiguous. It distinguishes from sibling 'create_milestone' by specifying 'group' context, though it doesn't explicitly contrast them.

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 like 'create_milestone' (likely for project-level milestones) or 'update_group_milestone'. The description implies it's for group milestones but doesn't clarify prerequisites, exclusions, or comparative use cases.

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