Skip to main content
Glama

Delete Issue

delete_issue
DestructiveIdempotent

Permanently remove a MantisBT issue by its numeric ID. This irreversible action deletes bug reports from the tracker system.

Instructions

Permanently delete a MantisBT issue. This action is irreversible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesNumeric issue ID to delete

Implementation Reference

  • Implementation of the 'delete_issue' tool handler, which calls the MantisBT API to delete an issue.
    server.registerTool(
      'delete_issue',
      {
        title: 'Delete Issue',
        description: 'Permanently delete a MantisBT issue. This action is irreversible.',
        inputSchema: z.object({
          id: z.coerce.number().int().positive().describe('Numeric issue ID to delete'),
        }),
        annotations: {
          readOnlyHint: false,
          destructiveHint: true,
          idempotentHint: true,
        },
      },
      async ({ id }) => {
        try {
          await client.delete<unknown>(`issues/${id}`);
          return {
            content: [{ type: 'text', text: `Issue #${id} deleted successfully.` }],
          };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: 'text', text: errorText(msg) }], isError: true };
        }
      }
    );
Behavior3/5

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

Annotations declare destructiveHint=true and idempotentHint=true. The description reinforces this with 'irreversible' and 'permanently', adding user-impact context. However, it omits side effects like cascading deletion of notes/attachments or relationships, which would be valuable behavioral detail beyond annotations.

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?

Two sentences with zero waste. First sentence states the action and resource; second provides critical safety warning. Perfectly front-loaded and appropriately sized for tool complexity.

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

Completeness4/5

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

For a single-parameter destructive operation with clear annotations and 100% schema coverage, the description adequately covers the essential behavioral warning (irreversibility). Minor gap regarding cascading effects on related entities (notes, attachments) or confirmation response details prevents a 5.

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 coverage is 100% with the 'id' parameter fully documented ('Numeric issue ID to delete'). The description does not add semantic details beyond the schema, but 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.

Purpose5/5

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

The description uses specific verb 'Permanently delete' with explicit resource 'MantisBT issue'. The 'irreversible' warning clearly distinguishes this from sibling update_issue and signals permanent removal versus deletion of sub-resources (like delete_note).

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The irreversibility warning provides implicit cautionary guidance, but lacks explicit 'when to use' criteria or alternatives (e.g., when to close/update instead of delete). No prerequisites or exclusions are stated.

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/dpesch/mantisbt-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server