Skip to main content
Glama
nulab

Backlog MCP Server

get_version_milestone_list

Retrieve version and milestone lists for Backlog projects to track project timelines and deliverables.

Instructions

Returns list of versions/milestones in the Backlog space

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe numeric ID of the project (e.g., 12345)
projectKeyNoThe key of the project (e.g., TEST_PROJECT)

Implementation Reference

  • The handler function that executes the tool logic: resolves the project using ID or key, then fetches the list of versions/milestones using backlog.getVersions().
    handler: async ({ projectId, projectKey }) => {
      const result = resolveIdOrKey(
        'project',
        { id: projectId, key: projectKey },
        t
      );
      if (!result.ok) {
        throw result.error;
      }
      return backlog.getVersions(result.value);
    },
  • Input schema definition using Zod: optional projectId (number) or projectKey (string).
    const getVersionMilestoneListSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_GET_VERSION_MILESTONE_PROJECT_ID',
            'The numeric ID of the project (e.g., 12345)'
          )
        ),
      projectKey: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_GET_VERSION_MILESTONE_PROJECT_KEY',
            'The key of the project (e.g., TEST_PROJECT)'
          )
        ),
    }));
  • Tool definition and registration within the exported getVersionMilestoneListTool function, including name, description, schemas, important fields, and handler.
    return {
      name: 'get_version_milestone_list',
      description: t(
        'TOOL_GET_VERSION_MILESTONE_LIST_DESCRIPTION',
        'Returns list of versions/milestones in the Backlog space'
      ),
      schema: z.object(getVersionMilestoneListSchema(t)),
      outputSchema: VersionSchema,
      importantFields: [
        'id',
        'name',
        'description',
        'startDate',
        'releaseDueDate',
        'archived',
      ],
      handler: async ({ projectId, projectKey }) => {
        const result = resolveIdOrKey(
          'project',
          { id: projectId, key: projectKey },
          t
        );
        if (!result.ok) {
          throw result.error;
        }
        return backlog.getVersions(result.value);
      },
    };
  • Final registration: adds the tool to the 'issue' toolset group in the allTools export.
    getVersionMilestoneListTool(backlog, helper),
  • Import of the getVersionMilestoneListTool for use in the toolset.
    import { getVersionMilestoneListTool } from './getVersionMilestoneList.js';
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states this is a read operation ('Returns list'), which implies non-destructive behavior, but doesn't address other critical aspects like authentication requirements, rate limits, pagination, sorting options, or error conditions. For a list-retrieval 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 immediately conveys the core functionality without unnecessary words. It's front-loaded with the main action and resource, making it easy to parse. Every element of the sentence serves a purpose, achieving maximum clarity with minimal verbiage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (list retrieval with two parameters), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic purpose but lacks behavioral context, usage guidance, and output format details. The 100% schema coverage helps with parameters, but overall completeness is limited by missing operational and contextual information.

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%, with both parameters ('projectId' and 'projectKey') clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema (e.g., it doesn't clarify whether both parameters are required, their relationship, or which takes precedence). With complete schema coverage, the baseline score of 3 is appropriate.

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 ('Returns list') and resource ('versions/milestones in the Backlog space'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_issues' or 'get_project_list', but the specificity of 'versions/milestones' provides inherent distinction. The description avoids tautology by not merely restating the tool name.

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. With siblings like 'get_project_list' and 'get_issues', there's no indication of whether this tool is for version tracking specifically versus general project data. No prerequisites, exclusions, or comparative context are mentioned, leaving usage decisions entirely to the agent's inference.

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