Pizza Developer

Delete project

delete_project

Destructive

Permanently delete a project and everything under it: Ideas, Batches, Works, Deliveries, Workflows, Rulesets, Instructions, Info, Dictionary, Features, and its Public Delivery Page. confirmName must equal the project's exact name. archive with kind project hides a project and keeps its records.

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

Input Schema

Name	Required	Description	Default
`id`	Yes	Id of the Project.
`confirmName`	Yes	The Project's exact name, to confirm deletion.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 9, 2026

addedInput schema / properties / confirmName

Added value: +{
+  "description": "The Project's exact name, to confirm deletion.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "id"
-]New value: +[
+  "id",
+  "confirmName"
+]

First observedOct 3, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantive context beyond them: the full cascade of destroyed dependent entities (Ideas, Batches, Works, Deliveries, Workflows, etc.), the permanence, and the confirmName equality requirement. That is exactly the extra behavioral detail a destructive tool benefits from.

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?

Front-loaded with the highest-consequence fact (permanent delete), then cascading scope, then the confirmation guard, then the alternative. The long entity list is justified by the destructive nature and every sentence earns its place.

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?

No output schema exists, and the annotations cover the safety profile; the description fills the remaining gaps (what is destroyed, the confirmation guard, the archive alternative) fully for a two-parameter destructive call.

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 coverage is 100% and both parameters are already documented ('Id of the Project', 'exact name, to confirm deletion'). The description's restatement of the confirmName constraint is redundant with the schema, so baseline 3 applies.

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 ('Permanently delete a project') with an explicit enumeration of the scope of destruction. It distinguishes itself from the 'archive' sibling rather than from the delete_* family, which are all child-resource deletions.

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?

Names the alternative ('archive with kind project hides a project and keeps its records') and the condition that selects it, so the agent can route between permanently deleting vs. hiding. It stops short of a fully directive 'use X when...' phrasing, but the contrast is clear and actionable.

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

All Pizza Developer tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?