past.dev

Delete a project

delete_project

DestructiveIdempotent

Deletes a project permanently and revokes every key it holds, as Delete on Settings › Projects does. Destructive: call it without confirm first, put the sentence it answers to the person, and call again with confirm: true only if they agree. The organization's last live project cannot be deleted. Needs project Admin.

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": {
      "confirm": "<confirm>"
    },
    "name": "delete_project"
  }
}

Input Schema

Name	Required	Description	Default
`confirm`	Yes	true only once the person has agreed to the sentence an unconfirmed call answered with.
`project`	No	The project's slug, exactly as list_projects returned it. Omit it only when the organization has one live project.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026
- changedInput schema / properties / project / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```
First observedOct 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare destructiveHint=true and idempotentHint=true; the description goes well beyond them by disclosing that every key is revoked, that a confirmation round-trip is mandatory, that the last live project is protected, and that Admin rights are required. No contradiction with the annotations.

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?

Four sentences, front-loaded with the destructive impact and the confirm protocol, with no filler. The confirmation instructions are somewhat wordy but each clause carries actionable information.

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, and the description compensates by explaining that an unconfirmed call answers with a sentence rather than deleting, plus the auth and last-project constraints. Nothing needed to invoke it safely is missing.

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 both param descriptions already explain the confirm handshake and the project-slug omission rule. The description restates that same guidance rather than adding format or edge-case detail, so baseline 3 is correct.

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?

States a specific verb and resource ('Deletes a project permanently and revokes every key it holds') and differentiates from the sibling archive_project by stressing permanence. The 'as Delete on Settings › Projects does' mapping grounds the semantics in the known UI action.

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?

Gives an explicit two-step protocol: call without confirm first, relay the returned sentence to the person, then call again with confirm: true only on agreement. It also names the blocking preconditions (last live project cannot be deleted, requires project Admin), so when-not-to-use is covered.

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

All past.dev tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?