Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

set_favorite

Mark items as favorites (favorite=true, default) or remove the favorite (favorite=false).

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>",
      "media_keys": "<media_keys>"
    },
    "name": "set_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
favoriteNotrue (default) or false.
media_keysYesLibrary media keys (AF1Qip...) from list_media / search_media, as a JSON array or comma-separated.
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. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden, and it discloses almost nothing: not that this is a mutation, not whether unfavoriting is reversible, not whether it is idempotent, and not what happens to invalid media keys. The notification_message parameter hints at a follow-up reply workflow that the description never explains.

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?

A single front-loaded sentence with the default behavior called out parenthetically; nothing is wasted. It is arguably too terse for the amount of behavior it leaves unexplained, but there is no filler.

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 four-parameter mutation tool with no annotations and no output schema, one sentence is thin: nothing is said about permissions, account scoping implications, partial-failure behavior across a batch of media_keys, or what the call returns.

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 all four parameters including the account/confirmation requirement and media key format are already documented in structured data. The description's favorite=true/false gloss largely restates the schema wording, adding only the outcome semantics of each value.

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?

The description names a specific verb+resource ("Mark items as favorites") and covers both directions of the operation via the favorite flag. It is clear what the tool does, but it does not distinguish itself from siblings such as add_to_album or archive_media, which are also bulk per-media mutations.

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?

The only guidance is the binary mode implied by favorite=true/false; there is no statement of when to prefer this over sibling operations, no prerequisites, and no warning that media keys must come first from list_media/search_media (that only appears in the schema).

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