Skip to main content
Glama
Nextcloud MCP Server

Nextcloud MCP Server

by stack74

List trash bin

nextcloud_list_trash
Read-onlyIdempotent

List deleted files and folders in a Nextcloud trash bin, newest first, with original locations and optional name filtering. Use results to identify items for restoration.

Instructions

List deleted files and folders in the user's trash bin, newest first, with their original location. Restore one with nextcloud_restore_from_trash (needs write access) or in the Nextcloud web interface.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nextcloud_list_trash"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoOnly items whose name contains this text (case-insensitive).
response_formatNo'markdown' for readable output, 'json' for structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds useful traits beyond that: sort order (newest first) and that entries carry their original location, plus the note that restoring requires write access. It says nothing about truncation or whether more results exist beyond the limit, which matters for a listing tool.

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, both earning their place: the first delivers purpose plus ordering and payload detail, the second delivers the actionable next step. Front-loaded with no filler.

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 read-only three-parameter listing tool with no output schema, the description covers purpose, sort order, and a key output field (original location). The notable omission is pagination/truncation behavior relative to the limit parameter.

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?

With schema coverage at 67%, the schema already documents 'query' and 'response_format'. The description adds no parameter-level meaning of its own, and 'limit' (1-500, default 50) remains undocumented in both places, so no compensation for the gap.

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 and resource ('List deleted files and folders in the user's trash bin') plus scope details (newest first, original location included). The trash-bin scope distinguishes it unambiguously from the file-listing and search siblings.

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?

Clear context is given: use this to see deleted items before restoring, and the next step is spelled out with the named sibling nextcloud_restore_from_trash plus a web-UI fallback. It stops short of explicit exclusions (e.g., use nextcloud_list_files for live files), so it isn't a full when/when-not routing rule.

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