Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

search_media

Search the library the way the Google Photos search box does: free text (sunset, food, beach), a person's name from People, a place, or a thing. Returns the same item shape as list_media.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "google_account_email": "<google_account_email>",
      "query": "<query>"
    },
    "name": "search_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch text, e.g. sunset, food, a named person, a city.
page_sizeNoMax results, 1-500. Default 100.
page_tokenNonext_page_token from the previous call.
google_account_emailYesThe signed-in Google account email whose Google Photos library to use (e.g. the one at /u/1/). Call list_accounts first and confirm with the user; do not guess.
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does useful work by defining accepted query forms and by stating the return shape matches list_media, but it says nothing about result ranking, pagination behavior beyond the token in the schema, or account scoping/limits, so a meaningful gap remains for an unannotated tool.

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

Conciseness5/5

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

Two compact sentences, front-loaded with the core behavior and ending with a genuinely useful pointer to the sibling whose item shape is reused. No filler or redundant restatement of the tool name.

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?

With no output schema, the description compensates by telling the agent to expect the same item shape as list_media, and the schema handles pagination and account parameters in full. What's missing is any statement of result ordering or scope behavior, which matters for a search tool, but overall it is sufficient to call correctly.

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 coverage is 100%, so the schema already documents all five parameters, including query examples and the account-selection warning. The description's query-type enumeration (free text, People name, place, thing) largely restates the schema's 'sunset, food, a named person, a city' example, adding only the 'from People' nuance, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource (search the media library) and defines the query space precisely with examples like sunset, a person's name from People, a place, or a thing. It implicitly separates itself from list_media by framing this as the 'search box' behavior and by pointing at list_media only for the return shape, though it never states the contrast explicitly.

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 'search box' analogy implies you use this when you have a text/person/place query rather than browsing everything, and the parenthetical examples make the intended use concrete. However, there is no explicit when-not-to-use or a named alternative such as list_media for unfiltered enumeration, leaving the routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources