Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_recycle_bin

Read-only

Lists deleted files and folders in a Synology shared folder's recycle bin, with optional pattern search across subfolders and paths to locate items for recovery.

Instructions

List what's in one shared folder's recycle bin: the files and folders deleted from that share. list_shares shows which shares have a bin; for files that weren't deleted, use list_files. Without pattern, only the bin's top level is listed, and DSM sorts folders and files separately, as in list_files. With pattern, the bin is searched, subfolders included (up to 200 folders and 5,000 items; the reply says when it stops early), and each match shows its path in the bin. Modified is the file's own time, not when it was deleted.

Input Schema

NameRequiredDescriptionDefault
limitNoMost items to return; `0` returns them all.
shareYesThe shared folder whose bin to list, as a name (`video`) or path (`/video`).
offsetNoItems to skip; a reply with more says which offset is next.
patternNoName filter, as in list_files (case-insensitive; `*` and `?`; a bare word matches anywhere), applied across the bin, subfolders included (up to 200 folders and 5,000 items; the reply says when it stops early).
sort_byNo`mtime` (default: the file's own modified time), `ctime` (closest to when it was deleted), `name`, `size`, `crtime` or `atime`.mtime
sort_directionNo`desc` (default) or `asc`.desc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.9.1
    • addedInput schema / properties / limit / description
      Added value: +"Most items to return; `0` returns them all."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Items to skip; a reply with more says which offset is next.",
+  "type": "integer"
+}
    • addedInput schema / properties / pattern / description
      Added value: +"Name filter, as in list_files (case-insensitive; `*` and `?`; a bare word matches anywhere), applied across the bin, subfolders included (up to 200 folders and 5,000 items; the reply says when it stops early)."
    • addedInput schema / properties / share / description
      Added value: +"The shared folder whose bin to list, as a name (`video`) or path (`/video`)."
    • addedInput schema / properties / sort_by / description
      Added value: +"`mtime` (default: the file's own modified time), `ctime` (closest to when it was deleted), `name`, `size`, `crtime` or `atime`."
    • addedInput schema / properties / sort_direction / description
      Added value: +"`desc` (default) or `asc`."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_list_recycle_binOutput",
-  "type": "object"
-}New value: +null
  2. Changed9 schema fields changedv0.7.0
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / pattern / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / pattern / default
      Removed value: -null
    • removedInput schema / properties / pattern / title
      Removed value: -"Pattern"
    • addedInput schema / properties / pattern / type
      Added value: +"string"
    • removedInput schema / properties / share / title
      Removed value: -"Share"
    • removedInput schema / properties / sort_by / title
      Removed value: -"Sort By"
    • removedInput schema / properties / sort_direction / title
      Removed value: -"Sort Direction"
    • removedInput schema / title
      Removed value: -"tool_list_recycle_binArguments"
  3. First observedv0.4.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantial behavioral detail beyond them: top-level-only listing without a pattern, folder/file sorting parity with list_files, recursive search with pattern, caps of 200 folders and 5,000 items, early-stop notification, path reporting per match, and the distinction between file mtime and deletion time. No behavior contradicts the annotations.

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?

The purpose and scope are front-loaded in the first sentence, followed by sibling routing and then behavioral nuances in a compact paragraph. Every sentence contributes distinct selection or invocation information, with no filler.

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

Completeness5/5

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

For a read-only listing tool with six parameters, full schema coverage, and no output schema, the description covers the important gaps: list behavior with and without pattern, search limits and early-stop signaling, path reporting, sorting, and the meaning of modified time. An agent has enough information to invoke it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines each parameter. The description still adds useful meaning: it explains how pattern changes scope (search across the bin, subfolders included), describes the search caps, and clarifies that 'modified' is the file's own time rather than deletion time. This goes beyond schema restatement, though much of it is behavioral context rather than per-parameter syntax.

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 opens with a specific verb and resource: 'List what's in one shared folder's recycle bin: the files and folders deleted from that share.' It explicitly distinguishes this tool from list_shares (which shares have a bin) and list_files (non-deleted files), so an agent can select it without opening the schema.

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

Usage Guidelines5/5

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

It names two concrete alternatives and the conditions that select them: list_shares for checking which shares have a bin, and list_files for files that were not deleted. That provides explicit routing guidance and a clear when-not condition.

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