Skip to main content
Glama
nulab

Backlog MCP Server

add_version_milestone

Create a new version milestone in Backlog projects to track release timelines. Specify project details and milestone dates for efficient project management.

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
organizationNoOptional organization name. Use list_organizations to inspect available organizations.

Implementation Reference

  • The handler function for the add_version_milestone tool. It resolves the project ID or key using resolveIdOrKey, then calls backlog.postVersions() to create the 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);
    },
  • Input schema definition using Zod. Defines fields: projectId (optional number), projectKey (optional string), name (required string), description (optional string), startDate (optional string), releaseDueDate (optional string).
    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 VersionSchema defines the output/response shape for version milestone operations. Used as the outputSchema for the add_version_milestone tool.
    export const VersionSchema = z.object({
      id: z.number(),
      projectId: z.number(),
      name: z.string(),
      description: z.string().optional(),
      startDate: z.string().optional(),
      releaseDueDate: z.string().optional(),
      archived: z.boolean(),
      displayOrder: z.number(),
    });
  • The resolveIdOrKey helper function used by the handler to resolve the project identifier (either numeric ID or string key) into a single value for the backlog API call.
    export const resolveIdOrKey = <E extends EntityName>(
      entity: E,
      values: { id?: number; key?: string },
      t: TranslationHelper['t']
    ): ResolveResult => resolveIdOrField(entity, 'key', values, t);
  • Registration of the addVersionMilestoneTool in the 'issue' tools group within the allTools function. It's listed alongside other version milestone tools.
    getVersionMilestoneListTool(backlog, helper),
    addVersionMilestoneTool(backlog, helper),
    updateVersionMilestoneTool(backlog, helper),
    deleteVersionTool(backlog, helper),
Behavior2/5

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

With no annotations, the description must disclose behavior. It only states the creation action, omitting side effects, required permissions, duplicate handling, or other constraints. The parameter description field confusingly repeats the same text.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is under-specified. It fails to convey necessary context like the relationship to projects or the expected outcome.

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 7 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what a version milestone is, how it ties to a project, or what happens upon success.

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 baseline clarity. The tool description adds no extra parameter context beyond the schema, but the schema descriptions (e.g., organization hinting at list_organizations) are adequate.

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 the resource (version milestone), but lacks differentiation from siblings like update_version_milestone or context about what a version milestone represents.

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, such as checking if a milestone already exists or prerequisites like a project context. The agent receives no situational advice.

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