Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List trash

drive_list_trash
Read-onlyIdempotent

List files and folders in the Proton Drive trash with pagination, returning metadata like names, paths, sizes, and unique IDs to identify items for restoration or deletion.

Instructions

List all files and folders in the Proton Drive trash. Returns {items, total, offset, limit, hasMore} (default limit 100, newest first, ties by uid); items are [{name, path, type, size?, storageSize?, modifiedAt?, uid, trashedAt?}]. Items come in a stable sorted order; each page is a fresh read, so changes between page calls can still shift items. Names are NOT unique in trash — uid and trashedAt tell duplicates apart. drive_restore/drive_delete accept the uid but refuse when the name is shared (the CLI cannot target one duplicate).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return (default 100).
offsetNoNumber of items to skip (default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.38
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max items to return (default 100).",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of items to skip (default 0).",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses sort order and tie-breaking (newest first, ties by uid), default page size, the fact that each page is a fresh read so items can shift between calls, and that names are non-unique so uid+trashedAt must disambiguate. It also flags that restore/delete refuse shared names — genuinely useful behavioral context.

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?

Dense but front-loaded, leading with what it does and the return shape before the caveats. Slightly packed with detail, but each clause (ordering, non-unique names, uid caveat) earns its place.

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?

With no output schema, the description fully describes the return shape ({items, total, offset, limit, hasMore}) and item fields, plus pagination caveats. An agent has everything needed to call and interpret it correctly.

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 100%, so the two parameters (limit, offset) are already documented in the schema; the description mostly repeats the default limit and adds sorting detail rather than new parameter syntax. Baseline 3 is appropriate.

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 all files and folders in the Proton Drive trash'), which distinguishes it from the sibling drive_list that lists non-trashed content. An agent can identify the operation 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 Guidelines4/5

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

The context is clear (this is trash listing, as opposed to drive_list), and it helpfully routes the agent by noting that drive_restore/drive_delete consume the returned uid. It does not explicitly state 'use drive_list for live files', but the framing makes the alternative inferable.

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