Skip to main content
Glama
nulab

Backlog MCP Server

add_version_milestone

Create version milestones in Backlog projects to track development timelines and release schedules. Define start dates, due dates, and descriptions for project planning.

Instructions

Creates a new version milestone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoProject ID
projectKeyNoProject key
nameYesVersion name
descriptionNoCreates a new version milestone
startDateNoStart date of the version
releaseDueDateNoRelease due date of the version

Implementation Reference

  • The async handler that resolves the project ID or key and calls the Backlog API to create a new version milestone.
    handler: async ({ projectId, projectKey, ...params }) => {
      const result = resolveIdOrKey(
        'project',
        { id: projectId, key: projectKey },
        t
      );
      if (!result.ok) {
        throw result.error;
      }
      return backlog.postVersions(result.value, params);
    },
  • Zod input schema for the tool parameters: projectId or projectKey, name, description, startDate, releaseDueDate.
    const addVersionMilestoneSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(t('TOOL_ADD_VERSION_MILESTONE_PROJECT_ID', 'Project ID')),
      projectKey: z
        .string()
        .optional()
        .describe(t('TOOL_ADD_VERSION_MILESTONE_PROJECT_KEY', 'Project key')),
      name: z
        .string()
        .describe(t('TOOL_ADD_VERSION_MILESTONE_NAME', 'Version name')),
      description: z
        .string()
        .optional()
        .describe(
          t('TOOL_ADD_VERSION_MILESTONE_DESCRIPTION', 'Version description')
        ),
      startDate: z
        .string()
        .optional()
        .describe(
          t('TOOL_ADD_VERSION_MILESTONE_START_DATE', 'Start date of the version')
        ),
      releaseDueDate: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_ADD_VERSION_MILESTONE_RELEASE_DUE_DATE',
            'Release due date of the version'
          )
        ),
    }));
  • The tool is instantiated and registered within the 'issue' toolset group.
    addVersionMilestoneTool(backlog, helper),
  • Import of the addVersionMilestoneTool function.
    import { addVersionMilestoneTool } from './addVersionMilestone.js';
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. While 'creates' implies a write/mutation operation, it doesn't specify permissions required, whether the operation is idempotent, what happens on conflicts, or what the response contains. For a creation 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 states the core purpose without unnecessary words. It's appropriately sized for a simple creation operation 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 creation tool with 6 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what a 'version milestone' is in this context, what happens after creation, or provide any behavioral context beyond the basic action. The combination of missing annotations and minimal description leaves too many gaps.

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 all parameters are documented in the schema itself. The description adds no additional parameter information beyond what's in the schema. The baseline score of 3 reflects adequate coverage through the schema alone, though the description contributes nothing extra.

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 'Creates a new version milestone' clearly states the action (creates) and resource (version milestone), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'add_project' or 'add_issue', which follow similar 'add/create' patterns for different resources.

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. There's no mention of prerequisites (e.g., needing a project context), when not to use it, or how it relates to sibling tools like 'update_version_milestone' or 'delete_version'.

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/nulab/backlog-mcp-server'

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