Skip to main content
Glama

delete_project

Permanently delete an entire project workspace, including all its collections, mock API endpoints, conditional rules, stateful Redis data, and captured request logs. WARNING: This action is irreversible. Before deleting, consider calling export_project if a backup of the project configuration might be needed.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYesDatabase ID of the project workspace to permanently delete (obtain from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"Database ID of the project to delete"New value: +"Database ID of the project workspace to permanently delete (obtain from list_projects)."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the whole burden and does well: it flags irreversibility in caps, lists the destructively removed entities, and points at a recovery/backup tool. It omits permission requirements and whether any confirmation or cascade-safety check occurs server-side.

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, front-loaded with the destructive scope, then the warning, then the alternative. Nothing is redundant and the ordering matches how an agent should reason before invoking it.

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

Completeness4/5

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

For a one-parameter destructive tool with no annotations and no output schema, the description covers scope, irreversibility, and the backup alternative. It could still say what the call returns (e.g., a confirmation or deleted ID) or whether dependent resources must be removed first.

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 projectId is the database ID obtainable from list_projects. The description only reinforces the scope ('entire project workspace') without adding format or sourcing detail beyond 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 ('Permanently delete') and resource ('an entire project workspace') and enumerates exactly what falls inside that scope: collections, mock endpoints, conditional rules, Redis state, and request logs. That cascade list distinguishes it cleanly from single-resource siblings such as delete_mock and delete_state.

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 a concrete pre-flight path by naming export_project as the alternative to call when a backup might be needed, which is exactly the decision an agent faces before a destructive call. It does not explicitly state when NOT to use it (e.g., deleting a single mock or clearing only state), so it stops short of full routing guidance.

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