mcp-gitlab-crunchtools

Overview Schema Source Related Servers Discussions Admin

Delete Pipeline Tool

delete_pipeline_tool

Delete a GitLab CI/CD pipeline and all its jobs permanently by providing the project ID or path and pipeline ID. This removes the selected pipeline and associated job records.

Instructions

Delete a CI/CD pipeline and all its jobs permanently.

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": {
      "project_id": "<project_id>",
      "pipeline_id": "<pipeline_id>"
    },
    "name": "delete_pipeline_tool"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes	Project ID or path
`pipeline_id`	Yes	Pipeline ID

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.0Oct 22, 2026
- addedInput schema / properties / pipeline_id / minimum
```
Added value: +1
```
First observedv0.4.1Aug 19, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose the two most important traits: the action is permanent and it cascades to all jobs. It omits other operationally relevant behavior — whether running pipelines can be deleted, required permission level, and whether any confirmation or force flag exists — which matters for an irreversible mutation.

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?

A single front-loaded sentence with no filler; the destructive scope is stated immediately after the verb. Every clause earns its place.

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

Completeness3/5

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

An output schema and fully documented parameters mean return values and inputs need no explanation, and the cascade/permanence note covers the core risk. For an unannotated irreversible delete, though, the definition should also say whether in-flight pipelines are affected and what permissions are needed before an agent commits to the call.

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% (project_id as ID or path, pipeline_id as integer >= 1), so the schema already handles parameter meaning. The description adds no syntax, format, or cross-parameter detail beyond that, warranting the baseline 3.

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

Purpose4/5

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

The description states a specific verb and resource ("Delete a CI/CD pipeline") and adds the cascade scope ("and all its jobs"), which meaningfully separates it from delete_job_tool and from cancel_pipeline_tool in the sibling list. It stops short of explicitly naming those alternatives, so it is clear but not fully differentiated.

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?

No guidance on when to use this versus cancel_pipeline_tool (stop but keep) or delete_job_tool (remove a single job). Nothing tells the agent what preconditions apply or when deletion is inappropriate, leaving selection entirely to inference from the name.

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

Deploy Server