Skip to main content
Glama
dipseth

google-workspace-unlimited

Optimized Album Sync

photos_optimized_album_sync
Read-onlyIdempotent

Sync and analyze Google Photos album contents with smart caching. Configure metadata analysis and limit items to process.

Instructions

Efficiently sync and analyze album contents with smart caching

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
album_idYesID of the album to sync. Required.
max_itemsNoMaximum items to process. Defaults to 200.
analyze_metadataNoWhether to analyze photo metadata. Defaults to True.
user_google_emailNoThe user's Google email address for Photos access. If None, uses the current authenticated user from FastMCP context (auto-injected by middleware).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if sync failed
successNoWhether the album sync operation succeeded
album_idYesID of the synced album
file_typesNoList of unique file types found in the album
user_emailNoEmail address of the user
years_spanNoList of years represented in the album content
cache_statsNoCache statistics for the sync operation
total_itemsNoTotal number of items in the album
photos_countNoNumber of photos in the album
text_summaryNoHuman-readable sync summary
videos_countNoNumber of videos in the album
cameras_detectedNoList of unique cameras used to capture album content
sync_time_secondsNoTime taken for the sync operation in seconds
Behavior2/5

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

Annotations already indicate readOnlyHint=true, idempotent, not destructive. The description adds 'smart caching' but does not explain what that entails or any potential side effects, adding little beyond the annotations.

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?

Extremely concise with one short sentence and no wasted words, but it lacks substantive information, which reduces its effectiveness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 4 parameters and an output schema, the description is too brief. It does not explain the syncing process, what 'smart caching' means, or the return behavior, leaving critical gaps.

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?

Input schema has 100% coverage with descriptions for all parameters. The description does not add further meaning to the parameters beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it syncs and analyzes album contents, which gives a general purpose, but the verb 'sync' is ambiguous and not differentiated from sibling tools like 'list_album_photos' or 'photos_batch_details'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, exclusions, or context where it is beneficial.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dipseth/google_workspace_fastmcp2'

If you have feedback or need assistance with the MCP directory API, please join our Discord server