Skip to main content
Glama

search_metadata

Search photos by location, camera details, date range, favorites, and media type using EXIF metadata in Immich photo library.

Instructions

Search photos by EXIF metadata: location (city/state/country), camera (make/model), date range, favorites, and type (IMAGE/VIDEO).

Args:
    city: Filter by city name (e.g. 'Barcelona', 'Cairo').
    state: Filter by state/region.
    country: Filter by country (e.g. 'Spain', 'Egypt').
    make: Camera manufacturer (e.g. 'Apple', 'Canon').
    model: Camera model (e.g. 'iPhone 14 Pro').
    taken_after: ISO date — only photos after this date.
    taken_before: ISO date — only photos before this date.
    is_favorite: Filter favorites only.
    asset_type: 'IMAGE' or 'VIDEO'.
    page: Page number (default 1).
    size: Results per page (default 50, max 200).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNo
stateNo
countryNo
makeNo
modelNo
taken_afterNo
taken_beforeNo
is_favoriteNo
asset_typeNo
pageNo
sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden. It describes the search functionality and pagination behavior (page/size parameters with defaults), but doesn't disclose rate limits, authentication requirements, error conditions, or what the output contains. The behavioral disclosure is basic but not comprehensive.

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?

The description is well-structured with a purpose statement followed by organized parameter documentation. Every sentence serves a purpose, though the parameter explanations could be slightly more concise. The front-loaded purpose statement effectively communicates core functionality.

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

Completeness4/5

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

Given the tool's complexity (11 parameters, no annotations) but with an output schema present, the description provides strong parameter semantics and clear purpose. It doesn't need to explain return values due to the output schema, but could better address behavioral aspects like error handling. Overall quite complete for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing detailed semantics for all 11 parameters. Each parameter gets clear explanations with examples (e.g., 'city: Filter by city name (e.g. 'Barcelona', 'Cairo')'), default values, and constraints (e.g., 'max 200' for size). This adds significant value beyond the bare schema.

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?

The description clearly states the tool's purpose with a specific verb ('Search') and resource ('photos by EXIF metadata'), listing key searchable attributes. It distinguishes this tool from siblings like 'search_smart' by specifying metadata-based filtering rather than smart/algorithmic search.

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?

The description implies usage through the listed search criteria but doesn't explicitly state when to use this tool versus alternatives like 'search_smart'. No guidance is provided on prerequisites, exclusions, or comparative effectiveness with sibling tools.

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/drolosoft/immich-photo-manager'

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