Skip to main content
Glama
nulab

Backlog MCP Server

delete_version

Remove a version from a Backlog project by specifying the version ID to manage project timelines and maintain accurate version tracking.

Instructions

Deletes a version from a project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdNoThe numeric ID of the project (e.g., 12345)
projectKeyNoThe key of the project (e.g., 'PROJECT')
idYesThe numeric ID of the version to delete (e.g., 67890)

Implementation Reference

  • Core implementation of the 'delete_version' tool as deleteVersionTool factory, defining name, schema, description, output schema, and the handler function that resolves the project ID/key and calls backlog.deleteVersions(projectId, versionId).
    export const deleteVersionTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof deleteVersionSchema>,
      (typeof VersionSchema)['shape']
    > => {
      return {
        name: 'delete_version',
        description: t(
          'TOOL_DELETE_VERSION_DESCRIPTION',
          'Deletes a version from a project'
        ),
        schema: z.object(deleteVersionSchema(t)),
        outputSchema: VersionSchema,
        handler: async ({ projectId, projectKey, id }) => {
          const result = resolveIdOrKey(
            'project',
            { id: projectId, key: projectKey },
            t
          );
          if (!result.ok) {
            throw result.error;
          }
          if (!id) {
            throw new Error(
              t('TOOL_DELETE_VERSION_MISSING_ID', 'Version ID is required')
            );
          }
          return backlog.deleteVersions(result.value, id);
        },
      };
    };
  • Zod schema definition for the delete_version tool inputs: optional projectId or projectKey, required version id.
    const deleteVersionSchema = buildToolSchema((t) => ({
      projectId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_DELETE_VERSION_PROJECT_ID',
            'The numeric ID of the project (e.g., 12345)'
          )
        ),
      projectKey: z
        .string()
        .optional()
        .describe(
          t(
            'TOOL_DELETE_VERSION_PROJECT_KEY',
            "The key of the project (e.g., 'PROJECT')"
          )
        ),
      id: z
        .number()
        .describe(
          t(
            'TOOL_DELETE_VERSION_ID',
            'The numeric ID of the version to delete (e.g., 67890)'
          )
        ),
    }));
  • Import of deleteVersionTool for registration.
    import { deleteVersionTool } from './deleteVersion.js';
  • Registration of deleteVersionTool instance in the 'issue' toolset of allTools.
    deleteVersionTool(backlog, helper),
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the destructive action ('Deletes') but doesn't mention critical details like permissions required, whether deletion is permanent/reversible, rate limits, or what happens to associated data. For a destructive tool with zero annotation coverage, this is a significant gap.

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 and front-loaded with the core action, making it easy for an agent to parse quickly.

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 destructive mutation tool with no annotations and no output schema, the description is incomplete. It should address behavioral aspects like safety, permissions, and consequences, especially given the tool's complexity and potential impact. The current description leaves too many unknowns for proper agent usage.

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 three parameters. The description doesn't add any meaning beyond what the schema provides about projectId, projectKey, or id parameters. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Deletes') and target ('a version from a project'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'delete_project' or 'delete_issue', which would require a 5.

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, exclusions, or related tools like 'add_version_milestone' or 'get_version_milestone_list', leaving the agent with no contextual usage information.

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