Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List album photos

photos_list_album_photos
Read-onlyIdempotent

List photos in a Proton Drive album with pagination; optionally include names, media types, sizes, capture times, and tags for each item.

Instructions

List the photos in an album. Returns {items, total, offset, limit, hasMore} (default limit 100, newest capture first, ties by nodeUid; without loadDetails there is no captureTime, so the order is by nodeUid); items are [{nodeUid}], or with loadDetails=true also name, mediaType, sizes, captureTime and tags. Items come in a stable sorted order; each page is a fresh read, so changes between page calls can still shift items. To add or remove photos use their /photos/ path, not the nodeUid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return (default 100).
offsetNoNumber of items to skip (default 0).
albumPathYesAlbum path, /albums/<name>.
loadDetailsNoInclude name, mediaType, sizes, captureTime and tags (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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>."
  2. Changed3 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 / loadDetails
      Added value: +{
+  "description": "Include name, mediaType, sizes, captureTime and tags (default false).",
+  "type": "boolean"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Number of items to skip (default 0).",
+  "minimum": 0,
+  "type": "integer"
+}
  3. Addedv1.0.26

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/idempotentHint, but the description goes far beyond: it discloses the return envelope, default limit, sort ordering (newest capture first, ties by nodeUid), the caveat that order collapses to nodeUid without loadDetails, and the important warning that each page is a fresh read so concurrent changes can shift items. That pagination-instability disclosure is exactly the kind of trait annotations cannot express.

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?

Front-loaded with the core action, then progressively layers return shape, ordering, and the mutation caveat — no sentence is filler. It is dense with parentheticals, though, which slightly hurts scannability for an agent parsing it quickly.

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 carries the full burden and does so: it names the response keys, item shape for both loadDetails modes, and the pagination contract. An agent has everything needed to call and interpret this tool without opening the schema.

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, but the description adds real semantics the schema lacks: it explains the interaction between loadDetails and captureTime availability, and that omitting loadDetails changes effective ordering to nodeUid. The only gap is that it restates the default limit already in the schema.

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?

Opens with a specific verb+resource ('List the photos in an album'), which cleanly separates it from photos_list_albums, photos_list_timeline, and photos_create_album. It further disambiguates by pointing out that add/remove operations belong to the /photos/ path, routing the agent away from photos_add_to_album/photos_remove_from_album.

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 final sentence explicitly routes mutation intent to a different tool family ('To add or remove photos use their /photos/ path'), which is genuine when-not guidance. However, it never states when to pick this over photos_list_timeline or how album-scoped listing relates to a global timeline listing.

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