Skip to main content
Glama

Google Photos MCP by Nova (CIVAI)

create_album

Create a new album with a title, optionally adding library items to it straight away.

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>",
      "title": "<title>"
    },
    "name": "create_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesAlbum title.
media_keysNoLibrary 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

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure and does very little: it does not state permission requirements, whether the album lands in a specific account, whether the operation is idempotent, or what the caller receives back. For a mutation tool with zero annotation coverage this is a notable gap, partially offset only by the schema's account-confirmation note.

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 well-formed sentence with the core action front-loaded and the optional behavior trailing as a qualifier. There is no redundancy, though the brevity comes at the cost of behavioral detail rather than being efficient under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The input side is fully covered by the rich schema, and no output schema exists so return values are not strictly required in the description. However, for a mutation tool with no annotations, an agent would benefit from knowing what identifier is returned to chain into add_to_album, and the description omits that.

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 the parameters including title, media_keys, google_account_email, and notification_message are already well documented. The description reinforces the optionality of media_keys ('optionally adding library items') but adds no syntax, format, or constraint detail beyond the schema.

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 uses a specific verb and resource ('Create a new album') and clarifies the scope of the operation, including the optional inline addition of library items. This distinguishes it implicitly from siblings like add_to_album (which adds to an existing album), though it does not name that sibling 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 phrase 'optionally adding library items to it straight away' implies the two usage patterns (create empty vs. create-and-populate, the latter being an alternative to create-then-add_to_album), but there is no explicit when-to-use guidance, no prerequisites, and no named alternative tool.

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