Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

archive_media

Archive items (they leave the main photo grid but stay in albums, search and Archive), or unarchive with archive=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": "archive_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
archiveNotrue (default) or false to unarchive.
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. Added
  4. Removed
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the disclosure burden and does well: it explains the visibility side effect (hidden from main grid, still present in albums/search/Archive) and that the operation is reversible via archive=false. It omits idempotency, behavior for already-archived items, and any limits on batch sizes.

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?

A single sentence, front-loaded with the action and its effect, then the inverse case. No padding or redundant phrasing.

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?

For a mutation tool with no annotations and no output schema, the description plus rich schema fields cover what an agent needs to call it correctly. Only minor gaps remain, such as idempotency and whether archived items can be re-archived or how bulk media_keys are handled on partial failure.

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 four parameters are already documented, including archive, media_keys formats, the account requirement, and the notification message fallback. The description only restates the archive=false semantic already present in the schema, adding no new parameter meaning.

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 (archive/unarchive) and resource (items), plus the concrete consequence: items leave the main photo grid but remain in albums, search and Archive. It does not name the sibling it differs from (e.g., trash_media), so the distinction from destructive removal must be inferred.

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?

Usage is implied rather than stated: the parenthetical explains what archiving does and the archive=false flag covers the reverse operation, but there is no explicit when-to-use guidance versus trash_media or removal from albums, and no stated prerequisites beyond what the schema says about the account.

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