Skip to main content
Glama

delete_project

Destructive

Permanently removes a closed project from the Resolve database; use it to clean up unused projects. The action is irreversible, so confirm the project is not open before deleting.

Instructions

Delete a project from the database (it must not be open). Irreversible.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
folderNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered, but the description adds real value by stating the operation is irreversible and by specifying the project must not be open at call time. It still omits whether media on disk is removed, whether child items are cascaded, and what permission level is needed.

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 short sentences with the precondition and the irreversibility warning front-loaded; nothing is redundant or padded.

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

Completeness3/5

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

For a simple destructive delete with no output schema, the precondition and irreversibility note cover the essentials of invoking it safely. The unexplained 'folder' parameter and the absence of any cascade or scope detail leave a meaningful gap given 0% schema coverage.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter explanations and it explains none. Neither the required 'name' nor the optional 'folder' is mentioned; in particular an agent cannot tell whether 'folder' scopes the lookup or causes the containing folder to be deleted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Delete a project") plus a scope qualifier ("from the database"), so the action is unambiguous. It does not distinguish itself from nearby siblings such as delete_project_folder or archive_project, leaving the agent to infer the difference from the names alone.

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?

"It must not be open" is a genuine precondition and rules out one class of misuse, which is more than most delete tools offer. However, it never names an alternative path for the cases it excludes (close_project, archive_project) or says when a project should be removed rather than archived.

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

Deploy Server

Other Tools