Skip to main content
Glama
dipseth

google-workspace-unlimited

Batch Photo Details

photos_batch_details
Read-onlyIdempotent

Retrieve detailed information for multiple photos in a single batch request, reducing API calls and improving efficiency.

Instructions

Get detailed information for multiple photos in a single optimized request

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
media_item_idsYesList of media item IDs to get details for. Required.
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 operation failed
successNoWhether the batch details operation succeeded
user_emailNoEmail address of the user
cache_statsNoCache statistics for the batch operation
failed_countNoNumber of photos that failed to retrieve details
failed_itemsNoList of items that failed to retrieve with error info
text_summaryNoHuman-readable summary of batch results
total_requestedNoTotal number of photo IDs requested
successful_countNoNumber of photos with successfully retrieved details
successful_itemsNoList of photos with successfully retrieved details
processing_time_secondsNoTime taken for the batch operation in seconds
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. The description adds only 'optimized request' without explaining what that entails (e.g., limits, caching). Minimal added value.

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

Conciseness3/5

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

Single sentence is concise but lacks structure. Every word is functional but could be more informative without increasing length significantly.

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

Completeness3/5

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

Output schema exists, so description need not explain return values. However, for a batch operation, details like maximum batch size or error handling are missing, making it minimally complete.

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 covers both parameters with descriptions. The description does not add additional meaning beyond what the schema already provides.

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?

Description clearly states the action (get detailed information) and scope (multiple photos) and distinguishes from sibling get_photo_details by specifying 'batch' and 'optimized'.

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

Usage Guidelines3/5

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

Description implies use for multiple photos but does not explicitly state when to use this over get_photo_details or any other alternative. No exclusions or context provided.

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