coolify-mcp

Delete project

deleteProject

Destructive

Delete a project by UUID, removing all its environments and resources in one operation.

Instructions

Delete a project by UUID. This will delete all environments and resources in the project.

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": {
      "uuid": "<uuid>"
    },
    "name": "deleteProject"
  }
}

Input Schema

Name	Required	Description	Default
`uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Aug 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description adds critical behavioral context beyond annotations: 'This will delete all environments and resources in the project.' This specifies the cascade scope of destruction, which is not captured by destructiveHint=true. This is valuable transparency for a destructive operation.

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?

The description is two concise sentences with no waste. It front-loads the action ('Delete a project') and provides the essential scope detail in the second sentence.

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?

For a simple destructive tool with one parameter and no output schema, the description is complete. It explains the action, the input method (UUID), and the full scope of deletion. Annotations already convey the destructive nature, and the description adds the specific cascade effect.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, but the description clarifies that the single 'uuid' parameter is used to identify the project to delete. This is sufficient for a one-parameter tool, adding meaning that the string must be a project UUID.

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 description states 'Delete a project by UUID' with a specific verb and resource, clearly identifying the action. It also distinguishes this tool from sibling delete tools (deleteApplication, deleteDatabase, etc.) by specifying the project entity.

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

Usage Guidelines3/5

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

The description implies usage (when you want to delete a project) but provides no explicit guidance on when to use this tool vs alternatives or when not to use it. It does not mention any exclusions or alternative tools for similar tasks.

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

Deploy Server