Skip to main content
Glama

delete_item

Delete files or directories in cPanel by moving them to Trash or permanently removing them; choose permanent deletion only when required.

Instructions

Move a file or directory to cPanel Trash, or permanently delete it.

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

Input Schema

NameRequiredDescriptionDefault
pathYesRelative path of the file or folder to delete.
permanentNoIf true, permanently deletes instead of moving to Trash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose the key behavioral distinction between trashing and permanent deletion, which is more than the schema alone conveys. However, it omits that permanent deletion is irreversible, whether trashed items are recoverable, and what happens on a missing path or insufficient permissions.

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?

A single front-loaded sentence with no filler; the two operational modes are presented together and nothing is wasted. It is appropriately sized for a two-parameter tool.

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 two-parameter tool with full schema coverage and no output schema, the description is adequate. The notable gap is the absence of any irreversibility warning for the destructive mode, which matters most for a delete tool with no annotations to signal destructiveness.

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%, so both parameters are already documented in structured data, establishing a baseline of 3. The description's mention of 'permanently delete' loosely reinforces the meaning of the 'permanent' flag but adds no syntax, path-format, or edge-case detail beyond the schema.

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 pairs a specific verb ('Move ... to Trash' / 'permanently delete') with a specific resource ('a file or directory'), so the operation is unambiguous. It does not explicitly distinguish itself from the sibling 'rename_or_move', which also moves files, though the delete framing and the name make the intent reasonably clear.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus 'rename_or_move' (which also moves paths) or how to choose between trash and permanent modes. No prerequisites, no warning about when permanent deletion is appropriate, and no exclusions are stated.

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