Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Download photo

photos_download

Download specific timeline photos from Proton Drive to a local folder using /photos/ paths; choose skip, rename, or remove for filename conflicts.

Instructions

Download photos from your timeline to a local folder by /photos/ path. /albums// paths are rejected by the CLI — use the /photos/ path. Timeline photos can share a filename: with conflictStrategy 'remove' or 'skip' only one copy survives locally; use 'rename' to keep all. Fails if any item fails. Requires confirmed=true when conflictStrategy is 'remove' (it deletes the existing LOCAL file).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedNoMust be true; only after the user approved this exact action.
photoPathsYesOne or more absolute photo paths to download (each must start with '/'). E.g. ['/photos/IMG_001.jpg']
localFolderYesAbsolute local destination folder (must start with '/'). Created if it does not exist.
conflictStrategyNo'skip' keeps the existing local file (default). 'rename' downloads under a unique name. 'remove' deletes the local file first — confirm with user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.2.0
    • changedInput schema / properties / confirmed / description
      Previous value: -"Must be true. Only set after the user explicitly approved this exact action."New value: +"Must be true; only after the user approved this exact action."
    • changedInput schema / properties / conflictStrategy / description
      Previous value: -"'skip' leaves an existing local file unchanged (default). 'rename' downloads under a unique name. 'remove' deletes the local file and downloads the remote copy in its place — confirm with user first."New value: +"'skip' keeps the existing local file (default). 'rename' downloads under a unique name. 'remove' deletes the local file first — confirm with user."
  2. Changed1 schema field changedv1.0.38
    • addedInput schema / properties / confirmed
      Added value: +{
+  "description": "Must be true. Only set after the user explicitly approved this exact action.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changedv1.0.32
    • changedInput schema / properties / conflictStrategy / description
      Previous value: -"How to handle local filename collisions. Defaults to 'skip'."New value: +"'skip' leaves an existing local file unchanged (default). 'rename' downloads under a unique name. 'remove' deletes the local file and downloads the remote copy in its place — confirm with user first."
    • changedInput schema / properties / conflictStrategy / enum
      Previous value: -[
-  "skip",
-  "replace",
-  "keep-both"
-]New value: +[
+  "skip",
+  "rename",
+  "remove"
+]
  4. Addedv1.0.28

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses atomic failure ('Fails if any item fails'), that 'remove' deletes the existing LOCAL file, and that confirmed=true is required for that path. The annotations only declare openWorldHint/destructiveHint, so this extra operational context is genuinely additive.

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 and front-loaded: path requirement first, then conflict behavior, then failure/confirmation constraints. Every sentence carries information, though the run-on conflict sentence is somewhat packed.

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?

With no output schema it adequately covers accepted input forms, conflict semantics, atomicity, and the confirmation gate needed for the destructive-by-local-file option. Minor gap: it doesn't state what comes back on success (e.g., per-file results) or partial-failure reporting beyond the all-or-nothing note.

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 already 100%, so the baseline is 3, but the description adds real semantics the schema lacks: that timeline photos can share a filename, that only one copy survives under 'skip'/'remove', and that 'rename' preserves all copies.

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+resource ('Download photos from your timeline to a local folder') and narrows scope with the required '/photos/<name>' path form. It also carves itself away from sibling operations like photos_upload/photos_list_timeline by describing the download direction and accepted path shape.

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?

Explicitly says album paths are rejected and to use the /photos/ path instead, and it tells the agent when to pick 'rename' vs 'skip'/'remove' for filename conflicts. It lacks routing to sibling tools (e.g., upload), but the when/when-not guidance for this tool's own options is strong.

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