Skip to main content
Glama
dipseth

google-workspace-unlimited

Smart Photo Search

photos_smart_search
Read-onlyIdempotent

Search and filter Google Photos by content categories and date range. Specify user email, include photos or videos, and set result limits.

Instructions

Advanced photo search with smart filtering and optimization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_endNoEnd date in YYYY-MM-DD format.
date_startNoStart date in YYYY-MM-DD format.
max_resultsNoMaximum results to return. Defaults to 50.
include_photosNoInclude photos in results. Defaults to True.
include_videosNoInclude videos in results. Defaults to False.
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).
content_categoriesNoContent categories (PEOPLE, ANIMALS, FOOD, etc.).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoError message if search failed
successNoWhether the search operation succeeded
user_emailNoEmail address of the user who performed the search
cache_statsNoCache statistics including size, hits, and performance metrics
media_itemsNoList of photos matching the search criteria
total_foundNoTotal number of matching photos found
text_summaryNoHuman-readable summary of search results
filters_appliedNoSearch filters that were applied (categories, dates, media types)
search_time_secondsNoTime taken for the search operation in seconds
Behavior2/5

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

The description adds minimal behavioral context beyond the annotations. While annotations already declare readOnlyHint=true and destructiveHint=false, the description's 'smart filtering and optimization' is too vague to inform the agent about actual behavior (e.g., how filtering works, performance implications).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is one short sentence, which is highly concise but underspecified. It fails to justify its existence by not adding meaningful information beyond the name and title.

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?

The description is incomplete for a complex tool with 7 parameters and an output schema. It does not explain how the parameters relate, what 'smart filtering' entails, or how the tool fits into the broader ecosystem of photo-related tools.

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%, so all 7 parameters have clear descriptions inline. The tool description does not add any additional parameter-level information, but baseline is 3 given full schema coverage.

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

Purpose2/5

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

The description 'Advanced photo search with smart filtering and optimization' is too vague. It does not specify what makes it 'smart' or how it differs from siblings like 'search_photos' or 'list_album_photos'. The verb 'search' is clear, but the resource (photos, albums, or both) is ambiguous.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or comparisons to other search tools, leaving the agent without decision support.

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