Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

remove_from_album

Remove items from an album. The photos stay in the library; only the album membership changes.

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>",
      "album_key": "<album_key>"
    },
    "name": "remove_from_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_keyYesAlbum key.
media_keysNoLibrary media keys (AF1Qip...) from list_media / search_media, as a JSON array or comma-separated.
album_item_keysNoOptional: album-item keys from list_albums(album_key) instead of library media keys.
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?

With no annotations, the description carries the full behavioral burden, and it does address the single biggest risk by stating that photos are preserved and only membership changes. However, it omits other relevant behavior: whether the call is idempotent, what happens with invalid or already-removed keys, and whether partial failures are possible across multiple keys.

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 short sentences, no filler, with the non-destructive scope front-loaded immediately after the purpose. Every sentence earns its place.

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 5-parameter mutation tool with no annotations and no output schema, the definition covers purpose and the key data-safety question, and the schema covers parameter semantics thoroughly. The remaining gap is what the caller gets back after a removal, which the description does not address.

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%, including guidance to call list_accounts before using google_account_email and the media_keys vs album_item_keys distinction, so the schema does the heavy lifting. The description adds no parameter meaning beyond that, making 3 the correct baseline.

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?

"Remove items from an album" states a specific verb and resource, and the follow-up sentence (“The photos stay in the library; only the album membership changes”) distinguishes it from destructive siblings like trash_media. It does not name a sibling alternative such as add_to_album, but the operation is unambiguous.

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 only implied by the verb — an agent can infer you call this when you want album membership removed. There is no explicit when-to-use/when-not, no mention of the inverse add_to_album, and no stated prerequisites about album ownership or required keys.

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