Skip to main content
Glama
googlarz

Proton Drive MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List photo timeline

photos_list_timeline
Read-onlyIdempotent

Browse your Proton Photos timeline with pagination to list photos newest first, including optional details like name, media type, and storage size.

Instructions

List photos in your full Proton Photos timeline. Returns {items, total, offset, limit, hasMore} (default limit 50, newest first, ties by nodeUid; each page is a fresh read, so changes between pages can shift items); items are [{nodeUid, captureTime, tags}], or with loadDetails=true also {name, mediaType, creationTime, totalStorageSize} (about 50% more tokens). Download by path with photos_download.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax items to return (default 50).
offsetNoNumber of items to skip (default 0).
loadDetailsNoIf true, fetch full node metadata for each photo instead of just its nodeUid. Default false.

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 50).",
+  "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. Addedv1.0.28

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds valuable behavior beyond annotations: pagination stability caveat ('each page is a fresh read, so changes between pages can shift items'), default page size, ordering rules, and token-cost impact of loadDetails.

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 efficiently packs return shape, pagination caveat, field variations, token cost, and an alternative. It is dense with parentheticals but every clause earns its place; minor run-on feel keeps it from a 5.

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?

No output schema exists, but the description fully explains the return shape, pagination behavior, field expansions, token tradeoff, and the relevant download alternative. Combined with annotations covering safety, an agent has everything needed to call 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 description coverage is 100%, so baseline is 3. The description adds meaningful details not in the schema: default limit 50, newest-first ordering with nodeUid tie-break, and loadDetails expanding items to include name, mediaType, creationTime, totalStorageSize at roughly 50% more tokens.

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: 'List photos in your full Proton Photos timeline.' This clearly distinguishes it from album-listing siblings by scope, and explicitly names photos_download as the tool for downloading.

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?

Gives clear context for when to use it (full timeline listing) and points to photos_download as an alternative for downloading. However, it does not explicitly contrast with photos_list_albums or photos_list_album_photos, leaving some inference to the agent.

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