photos_list_albumsList all Proton Photos albums with names, photo counts, shared status, creation time, and /albums/ paths for browsing or managing encrypted photo collections.
List all Proton Photos albums: [{name, photoCount, isShared, creationTime?}]. Album paths are /albums/.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.26Does 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 useful context: the response shape and the '/albums/<name>' path convention. It does not mention pagination or ordering, which is a minor omission for a list operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two compact sentences, front-loaded with the resource and scope, then the return shape and path format. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema exists, and the description compensates by listing the fields in the returned objects plus the album path convention. Only pagination/ordering behavior is left unspecified, which is a small gap for this simple read tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is nothing to disambiguate; baseline is 4. The description correctly indicates the operation is unfiltered (lists ALL albums).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('all Proton Photos albums') and even previews the returned fields. It separates albums from album photos implicitly, though it never names photos_list_album_photos as the sibling for a different resource.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to call this versus photos_list_timeline or photos_list_album_photos, and no stated preconditions (e.g. authentication). The agent must infer usage entirely from the name and the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.