gitlab-mcp

Delete Review App Environments

gitlab_delete_review_app_environments

Destructive

Detect stopped review-app environments older than a cutoff, preview candidates with dry-run, or schedule their deletion one week later.

Instructions

Find stopped review-app environments older than before (default 30 days ago) and, with dry_run=false, schedule their deletion one week later. dry_run defaults to true and only previews.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`before`	No
`dry_run`	No
`project_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.7.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare destructive and non-idempotent, but the description adds material facts not in them: deletion is scheduled one week after the call rather than immediate, and the safe preview is the default. It does not say what the preview output looks like or whether the scheduled window is configurable.

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 sentences, no filler, and the most consequential fact (dry_run defaults to true and only previews) is stated plainly. The scoping criteria come first and the mode behavior second.

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?

For a destructive, open-world tool with 0% schema coverage and no output schema, the description covers the riskiest behavior (deferred, off-by-default deletion) but omits what limit and project_id do and gives no sense of what the preview returns. Adequate but with clear gaps.

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 0%, so the description must carry the load. It explains `before` (defaults to 30 days ago) and `dry_run` (defaults true, previews only), but `limit` and `project_id` get no mention, leaving half the parameters undocumented everywhere.

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?

States a specific verb and scope: find stopped review-app environments past a threshold and schedule their deletion. This distinguishes it from gitlab_delete_environment (single environment) implicitly through 'review-app environments' and 'stopped ... older than', but no sibling is named to make the split explicit.

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?

Gives clear operating context: it targets stopped review apps older than a cutoff, and it tells the agent the safe default (dry_run=true previews, dry_run=false schedules deletion). No explicit when-not-to-use guidance or named alternative for non-review-app environments, which keeps it below a 5.

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

Deploy Server