@wanadev/mcp-gitlab

delete_file

Remove a file from a repository branch. Dry run mode provides a preview before committing the deletion.

Instructions

Delete a file from a repository. dry_run=true by default. This is destructive on the branch.

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>",
      "file_path": "<file_path>",
      "branch": "<branch>",
      "commit_message": "<commit_message>"
    },
    "name": "delete_file"
  }
}

Input Schema

Name	Required	Description
`project_id`	Yes	Project ID
`file_path`	Yes	File path in repository
`branch`	Yes	Branch to commit the deletion to
`commit_message`	Yes	Commit message
`dry_run`	No	Dry run mode (default: true). When true, returns a preview of the action without executing it. Set to false only after user confirmation.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.8.0Jun 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond annotation readOnlyHint=false, the description adds 'This is destructive on the branch' and explains dry_run behavior, providing full transparency about the tool's impact.

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 concise sentences with no unnecessary words. The key information (destructive, dry_run default) is front-loaded.

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?

No output schema exists; description partially covers return (preview for dry_run) but does not detail the response of actual deletion. Still adequate given the tool's simplicity.

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

Parameters4/5

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

Schema coverage is 100%, so description adds value by explaining dry_run default and advising to set false only after confirmation, which supplements the schema's static description.

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?

Description explicitly states 'Delete a file from a repository' with a clear verb and resource. This distinguishes it from sibling tools like create_file or update_file.

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?

Mentions dry_run=true by default and that the action is destructive, implying cautious usage. However, it does not explicitly state when to use this tool versus alternatives like commit_files.

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

Deploy Server