Skip to main content
Glama
Sign In
gitlab-mcp

gitlab-mcp

by mcpland
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Deployment

gitlab_delete_deployment
Destructive

Permanently deletes a GitLab deployment record by deployment_id; use a pre-check because GitLab blocks running deployments and an environment's latest deployment.

Instructions

Delete a deployment record permanently. GitLab refuses running deployments and the latest deployment of an environment. Requires deployment_id. Recommended pre-check: gitlab_get_deployment.

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": {
      "deployment_id": "<deployment_id>"
    },
    "name": "gitlab_delete_deployment"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNo
deployment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description goes beyond them by disclosing irreversibility and the specific server-side rejection rules (running deployments, latest deployment of an environment). Those refusal conditions are exactly the failure modes an agent needs to anticipate before calling a destructive tool.

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?

Three short sentences, front-loaded with the action and its permanence, then constraints, then the pre-check. Every sentence carries information an agent would otherwise have to discover at runtime.

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 destructive, non-idempotent tool the description covers impact, preconditions, and a verification path, which is nearly everything needed. The only meaningful gap is the undocumented project_id parameter and the absence of any note on what a successful response looks like (no output schema exists).

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, yet it only restates that deployment_id is required. The nullable project_id parameter is never mentioned, leaving the agent to guess whether it scopes the call or defaults to a configured project.

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?

States a specific verb and resource ('Delete a deployment record') plus the scope modifier 'permanently', which separates it from gitlab_update_deployment and the read-only gitlab_get_deployment at a glance. No ambiguity about what the tool acts on.

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?

Provides real operational guardrails: GitLab refuses running deployments and the latest deployment of an environment, and it explicitly recommends gitlab_get_deployment as a pre-check. It does not name a substitute for when deletion is refused (e.g., stop/cancel first), but the pre-check pointer covers most of the when-to-use need.

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