Skip to main content
Glama
Sign In
gitlab-mcp

gitlab-mcp

by mcpland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Group Iteration

gitlab_delete_group_iteration
Destructive

Permanently deletes a GitLab group iteration by group_id and iteration_id; issues lose the iteration and the action is irreversible. Requires group_id and iteration_id.

Instructions

Delete a group iteration permanently; issues lose the iteration. Irreversible. Requires group_id and iteration_id. Recommended pre-check: gitlab_list_group_iterations. Premium/Ultimate.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "group_id": "<group_id>",
      "iteration_id": "<iteration_id>"
    },
    "name": "gitlab_delete_group_iteration"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_idYes
iteration_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description earns credit for going beyond them: it names the collateral effect (issues lose the iteration), restates irreversibility, and discloses the Premium/Ultimate tier requirement. It does not cover permission scope or what happens to the iteration's other associations, which keeps it below a 5.

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 tight sentences: action and consequence first, then requirements, pre-check, and tier. Every clause carries distinct information with no redundancy.

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 two-parameter destructive tool with no output schema and full annotation coverage, the definition supplies the essentials: irreversibility, side effect on issues, prerequisite IDs, a verification sibling, and tier availability. Only parameter format and permission requirements are absent, which are minor given the tool's simplicity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only says 'Requires group_id and iteration_id' — a restatement of the schema's required list. It adds no format guidance (numeric ID vs. path, string encoding), which matters for a tool whose params are typed only as strings of maxLength 1024.

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 a specific verb and resource ('Delete a group iteration') and immediately states the operational consequence ('issues lose the iteration'), which makes the effect legible without opening the schema. The 'group' scoping plus the iteration-vs-cadence naming in siblings keeps it distinguishable from gitlab_delete_group_iteration_cadence.

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

Usage Guidelines4/5

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

It gives a concrete pre-call recommendation ('Recommended pre-check: gitlab_list_group_iterations') and flags the irreversible nature, which implicitly signals when caution is warranted. It stops short of stating explicit when-not-to-use conditions or contrasting with a safer alternative, so it is clear context rather than full routing guidance.

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

Deploy Server

Other Tools