Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Remove photo from album

photos_remove_from_album
Destructive

Removes a photo from a Proton Drive album while keeping it in your library and timeline. Requires explicit user approval and confirmed=true to proceed.

Instructions

Remove a photo from an album without deleting it from your library; it stays in the timeline. Requires confirmed=true after explicit user approval.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
albumPathYesAlbum path, /albums/<name>.
confirmedNoMust be true; only after the user approved this exact action.
photoPathYesPhoto path, /photos/<name>.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / albumPath / description
      Previous value: -"Absolute path of the album. Must start with /albums/. E.g. /albums/Vacation 2024"New value: +"Album path, /albums/<name>."
    • 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 / photoPath / description
      Previous value: -"Absolute path of the photo in the album. Must start with /photos/. E.g. /photos/IMG_001.jpg"New value: +"Photo path, /photos/<name>."
  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. Addedv1.0.26

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only provide destructiveHint=true, so the description usefully narrows what is destroyed: the photo leaves the album but remains in the library/timeline. It also discloses a required confirmation gate tied to prior user approval. It does not cover error behavior or whether the album order is preserved.

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 short clauses, front-loaded with the action and its non-destructive scope, then the confirmation requirement. No filler or redundant restatement of the name.

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 and only a single destructiveHint annotation, the description carries the needed safety context: scope of removal, library retention, and the approval gate. Adequate for a simple 3-parameter tool, though it omits any mention of failure modes or path-validation errors.

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 description coverage is 100%, and the schema already documents both path formats and the confirmed=true condition with its exact semantics. The description restates the confirmation rule rather than adding new parameter detail, so the baseline of 3 applies.

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 (remove a photo from an album) and immediately scopes it: the photo is not deleted from the library and stays in the timeline. This clearly separates it from photos_delete_album and drive_delete, which an agent could otherwise confuse it with.

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 description effectively states the context of use by contrasting removal-without-deletion with the destructive alternative, and it names the confirmed=true precondition tied to explicit user approval. It does not, however, explicitly name the sibling tool an agent should use instead when a true deletion is wanted.

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