Skip to main content
Glama
nulab

Backlog MCP Server

get_version_milestone_list

Retrieve a list of versions and milestones for a Backlog project by providing the project ID or key.

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

Implementation Reference

  • The handler function that executes the tool logic. It resolves projectId/projectKey via resolveIdOrKey, then calls backlog.getVersions() to retrieve version/milestone list.
    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. Accepts optional 'projectId' (number) and 'projectKey' (string) parameters.
    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)'
          )
        ),
    }));
  • Output schema (VersionSchema) defining the structure of each version/milestone returned: id, projectId, name, description, startDate, releaseDueDate, archived, displayOrder.
    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(),
    });
  • Registration of get_version_milestone_list tool within the 'issue' toolset, instantiated with backlog and helper.
      getVersionMilestoneListTool(backlog, helper),
      addVersionMilestoneTool(backlog, helper),
      updateVersionMilestoneTool(backlog, helper),
      deleteVersionTool(backlog, helper),
    ],
  • Helper utility resolveIdOrKey used by the handler to resolve either a numeric project ID or a string project key.
    export const resolveIdOrKey = <E extends EntityName>(
      entity: E,
      values: { id?: number; key?: string },
      t: TranslationHelper['t']
    ): ResolveResult => resolveIdOrField(entity, 'key', values, t);
Behavior1/5

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

No annotations are provided, and the description only says 'Returns list', offering no behavioral details such as read-only nature, authentication requirements, rate limits, or output format.

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, front-loaded sentence of 8 words with no superfluous content. Every word contributes to conveying the tool's purpose.

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 the absence of annotations and output schema, the description is too sparse. It does not indicate that the list is filterable by project ID/key, nor does it mention any pagination or result structure, leaving significant gaps for an AI agent.

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?

The input schema has 100% description coverage, with each parameter described clearly. The description adds no extra meaning beyond the schema, so 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.

Purpose5/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 the resource (versions/milestones in the Backlog space). It is specific and distinct from sibling tools, which are primarily CRUD operations on issues, projects, or pull requests.

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?

There is no guidance on when to use this tool versus alternatives like get_project_list or add_version_milestone. The description does not mention any prerequisites or exclusions.

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