Skip to main content
Glama
nulab

Backlog MCP Server

update_version_milestone

Modify version milestones in Backlog projects to track progress, adjust timelines, or update details like names, dates, and archive status.

Instructions

Updates an existing version milestone

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe numeric ID of the project (e.g., 12345)
projectKeyNoThe key of the project (e.g., 'PROJECT')
idYesVersion ID
nameYesVersion name
descriptionNoUpdates an existing version milestone
startDateNoStart date
releaseDueDateNoRelease due date
archivedNoArchive status of the version

Implementation Reference

  • The core tool definition including the inline handler function that resolves the project ID or key and calls `backlog.patchVersions` to update the version milestone.
    export const updateVersionMilestoneTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof updateVersionMilestoneSchema>,
      (typeof VersionSchema)['shape']
    > => {
      return {
        name: 'update_version_milestone',
        description: t(
          'TOOL_UPDATE_VERSION_MILESTONE_DESCRIPTION',
          'Updates an existing version milestone'
        ),
        schema: z.object(updateVersionMilestoneSchema(t)),
        outputSchema: VersionSchema,
        importantFields: [
          'id',
          'name',
          'description',
          'startDate',
          'releaseDueDate',
          'archived',
        ],
        handler: async ({ projectId, projectKey, id, ...params }) => {
          const result = resolveIdOrKey(
            'project',
            { id: projectId, key: projectKey },
            t
          );
          if (!result.ok) {
            throw result.error;
          }
          return backlog.patchVersions(result.value, id, params);
        },
      };
    };
  • Zod schema definition for the input parameters of the update_version_milestone tool, including project ID/key, version ID, name, description, dates, and archived status.
    const updateVersionMilestoneSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_VERSION_MILESTONE_PROJECT_ID',
            'The numeric ID of the project (e.g., 12345)'
          )
        ),
      projectKey: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_VERSION_MILESTONE_PROJECT_KEY',
            "The key of the project (e.g., 'PROJECT')"
          )
        ),
      id: z.number().describe(t('TOOL_UPDATE_VERSION_MILESTONE_ID', 'Version ID')),
      name: z
        .string()
        .describe(t('TOOL_UPDATE_VERSION_MILESTONE_NAME', 'Version name')),
      description: z
        .string()
        .optional()
        .describe(
          t('TOOL_UPDATE_VERSION_MILESTONE_DESCRIPTION', 'Version description')
        ),
      startDate: z
        .string()
        .optional()
        .describe(t('TOOL_UPDATE_VERSION_MILESTONE_START_DATE', 'Start date')),
      releaseDueDate: z
        .string()
        .optional()
        .describe(
          t('TOOL_UPDATE_VERSION_MILESTONE_RELEASE_DUE_DATE', 'Release due date')
        ),
      archived: z
        .boolean()
        .optional()
        .describe(
          t(
            'TOOL_UPDATE_VERSION_MILESTONE_ARCHIVED',
            'Archive status of the version'
          )
        ),
    }));
  • Import of the updateVersionMilestoneTool.
    import { updateVersionMilestoneTool } from './updateVersionMilestone.js';
  • Registration of the tool in the 'issue' toolset group within allTools function.
    updateVersionMilestoneTool(backlog, helper),
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 offers minimal behavioral insight. It states 'Updates an existing version milestone' which implies a mutation operation, but doesn't disclose required permissions, whether changes are reversible, rate limits, or what happens to unspecified fields. For a mutation tool with zero annotation coverage, this is inadequate.

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 tool with comprehensive schema documentation and gets straight to the point 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 8 parameters, no annotations, and no output schema, the description is insufficient. It doesn't address what the tool returns, error conditions, side effects, or how it interacts with the system. The agent lacks crucial context for proper invocation despite good schema coverage.

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 the schema already documents all 8 parameters thoroughly. The description adds no additional meaning beyond what's in the schema - it doesn't explain parameter relationships, constraints, or usage patterns. Baseline 3 is appropriate when the schema does all the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Updates an existing version milestone' clearly states the action (update) and resource (version milestone), but it's vague about what specifically gets updated. It doesn't differentiate from sibling tools like 'update_issue' or 'update_project' beyond the resource name, and lacks specificity about the scope of updates.

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 scenarios, or how it differs from similar update tools in the sibling list. This leaves the agent without context for tool selection.

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