Skip to main content
Glama

project_delete

DestructiveIdempotent

Request deletion of a project. Two-step flow.

Step 1 — project_delete takes just the project_id. The platform returns a 6-digit confirmation code that expires after 10 minutes. No project state changes before the code is confirmed.

Step 2 — Human authorization is required before calling project_delete_confirm with the same project_id and code. Confirmation immediately takes the project and its hostnames offline, blocks new project effects, retains its database, files, functions, environment variables, and domain bindings for 30 days, and schedules permanent erasure after that retention period. Recovery during the retention period requires support.

Example:

{ "project_id": "my-saas" }

The response is a SUCCESS carrying the code and a machine-readable status, e.g. { "ok": true, "status": "needs_confirmation", "confirmation_code": "482917", "code": "482917", "next_call": { "tool": "project_delete_confirm", ... } } — minting the code is this step's whole job, so it is never an error. The response carries confirmation_code (code is the same value, kept for existing callers). The response carries no error_code and no canonical_error, so branching on those stays a reliable failure test.

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>"
    },
    "name": "project_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotentHint=true, but the description adds substantial context beyond them: no state change on step 1, code expiry at 10 minutes, immediate offline of project and hostnames on confirm, 30-day retention of database/files/functions/env vars/domain bindings, and permanent erasure after that. It also clarifies that minting a code is never an error and that absence of error_code/canonical_error is the reliable failure signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Structure is strong: numbered steps, bolded two-step label, example request, and an annotated response sample are all front-loaded and scannable. It is longer than needed — the parenthetical about `code` being kept for existing callers and the meta note about branching on error fields could be trimmed without loss.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so fully: it shows the success shape with ok, status, confirmation_code, code, and next_call. Combined with the retention and authorization behavior, an agent has everything needed to call step 1 and hand off to step 2 correctly.

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% and the schema already explains that project_id accepts UUID, subdomain, slug, or 'default' with multi-project disambiguation. The description adds only an example payload and the fact that the same project_id must be reused in step 2, which is marginal beyond the schema.

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?

The first sentence states a specific verb and resource ('Request deletion of a project'), and the rest immediately scopes it as step 1 of a two-step flow, explicitly naming project_delete_confirm as the other half. An agent can distinguish this from the confirm tool and from siblings like project_archive without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use mechanics (call with just project_id, receive a code, obtain human authorization, then call project_delete_confirm with the same project_id and code) and when-not implications (no state changes before confirmation). The 10-minute expiry and the support-only recovery path bound the decision further.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources