Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Delete permanently

drive_delete
Destructive

Permanently deletes an item already in Proton Drive trash, requiring confirmed=true and a trash path or uid; irreversible, so confirm the exact path first.

Instructions

Permanently delete a file or folder already in the Proton Drive trash — irreversible. The CLI only accepts items inside /trash or /photos-trash, so drive_trash first, then pass the trash path (or uid from drive_list_trash). If several trashed items share the name, this refuses and lists their uids: the CLI can only address trashed items by name, so use the Proton Drive web or desktop app for that. Requires confirmed=true; show the exact path to the user first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidNoTrash uid from drive_list_trash; if path is also given they must match.
pathNoTrash path to delete permanently. Give path or uid (or both).
confirmedYesMust be true; the user has acknowledged this is permanent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • changedInput schema / properties / confirmed / description
      Previous value: -"Must be true. Confirms the user has acknowledged this deletion is permanent and cannot be undone."New value: +"Must be true; the user has acknowledged this is permanent."
    • changedInput schema / properties / path / description
      Previous value: -"Absolute remote Drive path to permanently delete (must start with '/')."New value: +"Trash path to delete permanently. Give path or uid (or both)."
    • addedInput schema / properties / uid
      Added value: +{
+  "description": "Trash uid from drive_list_trash; if path is also given they must match.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "path",
-  "confirmed"
-]New value: +[
+  "confirmed"
+]
  2. Changed2 schema fields changedv0.1.2
    • changedInput schema / properties / confirmed / description
      Previous value: -"Must be true. Confirms the user has acknowledged this is permanent."New value: +"Must be true. Confirms the user has acknowledged this deletion is permanent and cannot be undone."
    • changedInput schema / properties / path / description
      Previous value: -"Remote Drive path to delete."New value: +"Absolute remote Drive path to permanently delete (must start with '/')."
  3. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds substantial context beyond that: the operation is irreversible, only /trash or /photos-trash paths are accepted, the CLI can only address trashed items by name, and ambiguous names trigger a refusal that returns uids.

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 irreversible warning and required flag are front-loaded and every sentence carries actionable information. It is slightly dense with parenthetical clauses, but nothing is 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 destructive 3-parameter tool with no output schema, the description covers prerequisites, failure modes, safety gating, and fallback advice, so an agent has everything needed 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 baseline is 3; the description adds operational meaning by tying uid to drive_list_trash and requiring confirmed=true as an explicit user acknowledgment. It also surfaces the name-collision constraint that makes path vs uid selection non-trivial.

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 (permanently delete a file or folder) and immediately scopes it to items already in the trash, marking it irreversible. This cleanly separates it from siblings drive_trash (soft delete) and drive_empty_trash (bulk wipe).

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?

Explicitly prescribes the workflow: drive_trash first, then pass the trash path or a uid from drive_list_trash. It also names when to abandon the tool entirely (duplicate trashed names — use the web/desktop app) and requires confirmed=true with the path shown to the user first.

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