Skip to main content
Glama
nulab

Backlog MCP Server

delete_issue

Remove issues from Backlog project management by specifying either the issue ID or issue key. This tool permanently deletes issues to help maintain organized project workflows.

Instructions

Deletes an issue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueIdNoThe numeric ID of the issue (e.g., 12345)
issueKeyNoThe key of the issue (e.g., 'PROJ-123')

Implementation Reference

  • Full implementation of the 'delete_issue' tool factory, defining name, input/output schemas, description, and the handler logic that resolves the issue identifier and calls the Backlog API to delete it.
    export const deleteIssueTool = (
      backlog: Backlog,
      { t }: TranslationHelper
    ): ToolDefinition<
      ReturnType<typeof deleteIssueSchema>,
      (typeof IssueSchema)['shape']
    > => {
      return {
        name: 'delete_issue',
        description: t('TOOL_DELETE_ISSUE_DESCRIPTION', 'Deletes an issue'),
        schema: z.object(deleteIssueSchema(t)),
        outputSchema: IssueSchema,
        handler: async ({ issueId, issueKey }) => {
          const result = resolveIdOrKey('issue', { id: issueId, key: issueKey }, t);
          if (!result.ok) {
            throw result.error;
          }
          return backlog.deleteIssue(result.value);
        },
      };
    };
  • Input schema definition for the delete_issue tool, supporting either issue ID (number) or issue key (string).
    const deleteIssueSchema = buildToolSchema((t) => ({
      issueId: z
        .number()
        .optional()
        .describe(
          t(
            'TOOL_DELETE_ISSUE_ISSUE_ID',
            'The numeric ID of the issue (e.g., 12345)'
          )
        ),
      issueKey: z
        .string()
        .optional()
        .describe(
          t('TOOL_GET_ISSUE_ISSUE_KEY', "The key of the issue (e.g., 'PROJ-123')")
        ),
    }));
  • Registration of the delete_issue tool within the 'issue' toolset group in the allTools function.
    deleteIssueTool(backlog, helper),
  • Import of the delete_issue tool for registration.
    import { deleteIssueTool } from './deleteIssue.js';
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. 'Deletes an issue' implies a destructive mutation but lacks critical details: whether deletion is permanent or reversible, what permissions are required, if it affects related data (e.g., comments), or what happens on success/failure. This is inadequate for a destructive tool with zero annotation coverage.

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 extremely concise at just two words, with zero wasted language. It's front-loaded with the core action, though this brevity contributes to its inadequacy in other dimensions.

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 severely incomplete. It fails to address behavioral risks, success criteria, error conditions, or relationships to other tools, leaving the agent with insufficient context to use it safely or effectively.

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 ('issueId' and 'issueKey') clearly documented in the schema. The description adds no parameter-specific information beyond implying an 'issue' is involved, so it meets the baseline of 3 where the schema does the heavy lifting.

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

Purpose2/5

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

The description 'Deletes an issue' is a tautology that merely restates the tool name without adding specificity. It doesn't distinguish this deletion operation from other destructive operations like 'delete_project' or 'delete_version' among the sibling tools, nor does it clarify what constitutes an 'issue' in this context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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. It doesn't mention prerequisites (e.g., needing an existing issue), exclusions, or relationships to sibling tools like 'get_issue' for verification or 'update_issue' for modification instead of deletion.

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