Skip to main content
Glama

Delete item

nextcloud_delete_item
DestructiveIdempotent

Delete a file or folder from Nextcloud by moving it to the trash bin; specify the path and optionally confirm this destructive action.

Instructions

Delete one file or folder (it moves to the trash bin).

DELETE /remote.php/dav/files/{user}/{path}

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": "nextcloud_delete_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.2
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.",
      +  "type": "boolean"
      +}
  2. First observedv2.3.4

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare the operation destructive, non-read-only, idempotent, and open-world. The description adds important behavioral context beyond those annotations by explaining that deletion moves the item to the trash bin, implying recoverability. It does not cover permissions, recursive folder behavior, or failure modes, but it adds real value on top of the structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the essential operation and trash-bin behavior. The HTTP endpoint line is compact but is mostly an implementation detail, so the text is not perfectly maximally concise, though it does not waste much space.

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 destructive file/folder deletion tool, the description covers the core behavior and recoverability via the trash bin, and annotations plus schema cover the safety profile and confirmation flag. However, it leaves meaningful gaps around folder recursion, permissions, and error behavior that an agent might need before invoking a destructive operation.

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 50%, with the confirm parameter documented in the schema and the path parameter undocumented there. The description's endpoint template clarifies that path is relative to the user's files area, which adds some meaning, but it does not specify path formatting details or further explain the confirm behavior beyond the schema's own description.

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 a specific verb and resource: delete one file or folder. It also names the effect, moving the item to the trash bin, which clearly distinguishes it from permanent deletion and from the many sibling tools that delete other resource types such as boards, notes, or users.

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?

Usage is implied by 'Delete one file or folder,' but the description does not explicitly say when to use this tool versus alternatives such as nextcloud_move_item or nextcloud_restore_trash_item. It also does not state exclusions, such as whether it works on non-empty folders or whether it can permanently delete items.

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