Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

trash_media

Move items to Google Photos' Trash, where they stay recoverable for 60 days. Never deletes permanently and cannot empty the Trash. Requires confirm=true; max 50 items per call. Show the user the exact items and get their yes first.

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>",
      "confirm": "<confirm>"
    },
    "name": "trash_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true, after the user approved the exact items.
media_keysYesUp to 50 library media keys to move to Trash, 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

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the 60-day recoverability window, that it never permanently deletes, that it cannot empty the Trash, and the 50-item cap per call. It omits auth/permission requirements, rate limits, and what happens on partial failure or already-trashed items, which keeps it from a 5.

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?

Four short sentences, each carrying distinct information: destination and recovery window, non-destructiveness, hard limits, and the approval workflow. The most consequential facts (trash, 60 days, irreversible-empty) are front-loaded with no filler.

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 covers destination, recoverability, limits, and the required user-approval flow, which is enough to call it safely. It stops short of describing the response or error behavior, a minor gap given no output schema exists.

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 are already documented, including the confirm and google_account_email guidance. The description only reinforces confirm=true and the 50-item limit and says nothing about notification_message, so it adds little beyond the schema — baseline 3.

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 states a specific verb and resource — moving items to Google Photos' Trash — and immediately qualifies the semantics (recoverable 60 days, never permanent). An agent can distinguish this from reversible organizational tools like archive_media or add_to_album because the destination and consequences are named explicitly.

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

Usage Guidelines4/5

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

It gives a clear precondition (confirm=true) and an explicit interaction protocol: show the user the exact items and get their yes first. It does not name an alternative tool (e.g., archive_media) for when the user wants to hide rather than trash items, so routing guidance is implied rather than complete.

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