gitlab-api

Delete snippet

gitlab_delete_snippet

DestructiveIdempotent

Deletes a GitLab snippet by ID or project, with an explicit confirmation option for destructive actions.

Instructions

Delete a snippet.

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_snippet"
  }
}

Input Schema

Name	Required	Description
`data`	No
`title`	No
`confirm`	No	Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.
`content`	No
`file_name`	No
`project_id`	No
`snippet_id`	No
`visibility`	No

Schema Changelog

Changes observed during successful MCP inspections.

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, so the danger profile is covered structurally. The description adds nothing beyond that: it does not mention irreversibility, the confirm flag required when a client cannot answer a prompt, or that deletion requires identifying the snippet via snippet_id/project_id. No contradiction, but no value added.

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 and front-loaded, but this is under-specification rather than conciseness. The one sentence that exists carries no information an agent could not get from the tool name.

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, eight-parameter, zero-required-parameter tool with no output schema and almost no schema descriptions, the description supplies nothing an agent needs to call it safely or correctly. This is far below the minimum viable bar for a mutation tool.

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?

There are 8 parameters with only 13% schema description coverage, and the description explains none of them. The critical question of whether snippet_id alone suffices or whether project_id is needed, plus the role of confirm, is left entirely undocumented in the prose.

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 is "Delete a snippet." which simply restates the tool name and title with no additional detail about what a snippet is, which snippet is targeted, or how deletion is scoped (project vs personal). It is a tautology rather than a distinguishing 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?

No when-to-use guidance is offered, and no alternatives are mentioned even though siblings like gitlab_update_snippet, gitlab_get_snippet, and gitlab_create_snippet exist and deletion is the irreversible option among them. An agent must infer everything from the tool name.

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

Deploy Server