gitlab-api

Delete issue

gitlab_delete_issue

DestructiveIdempotent

Delete a GitLab issue by project and issue IID, with confirmation support for the destructive action. Use it to remove obsolete or duplicate issues from a repository.

Instructions

Delete an issue.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gitlab_delete_issue"
  }
}

Input Schema

Name	Required	Description
`data`	No
`page`	No
`state`	No
`title`	No
`labels`	No
`confirm`	No	Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
`group_id`	No
`per_page`	No
`issue_iid`	No
`max_pages`	No
`project_id`	No
`description`	No
`state_event`	No
`assignee_ids`	No
`milestone_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv27.3.20Nov 7, 2026

removedInput schema / properties / api_parameters

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}

Changed1 schema field changedv27.3.18Nov 6, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "description": "Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.",
+  "type": "boolean"
+}

First observedv27.3.13Oct 25, 2026

TDQS

D1.8/5.0

Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, but the description adds no behavioral context such as irreversibility, required permissions, or effects on linked data. It neither contradicts nor enriches the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is short but under-specified rather than concise; it omits essential structure and front-loaded context for a destructive operation. Every sentence should earn its place, and this one only repeats the title.

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

Completeness1/5

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

For a destructive delete tool with 15 parameters, no output schema, and sparse schema descriptions, the definition is far too thin. It does not explain required identifiers, confirmation behavior, or side effects, leaving the agent unable to call it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 15 parameters with only 7% description coverage, and the description mentions none of them—not project_id, issue_iid, or confirm. It provides no meaning beyond the schema and fails to compensate for the low coverage.

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 "Delete an issue." restates the tool name and title without adding scope, target identifiers, or differentiation from siblings like gitlab_update_issue or gitlab_delete_note. It is a tautology rather than a meaningful purpose statement.

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 gitlab_update_issue, gitlab_get_issue, or other delete tools, and no prerequisites or exclusions are stated. The only implied usage comes from the verb "delete."

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server