Skip to main content
Glama

Photos Album Delete

photos_album_delete
Destructive

Permanently remove a personal album while keeping its photos in your library. Confirm with the user first by naming the album and photo count.

Instructions

Delete one of the person's own albums; its photos stay in the library, but the album cannot be brought back. Ask the person first, naming the album and how many photos it holds. Returns the album and deleted (read back: the album no longer opens). Shared albums are deleted or left in the app.

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": {
      "album_id": "<album_id>"
    },
    "name": "photos_album_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idYesAn album id from photos_albums

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.3

TDQS

A3.8/5.0
Behavior5/5

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

Annotations already flag destructive and non-idempotent, and the description still adds substance: photos survive the deletion, the album is unrecoverable, and it reports how verification works ('read back: the album no longer opens'). The confirmation requirement is behavioral context no structured field carries.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the confirmation rule are correctly front-loaded, but the phrasing degrades toward the end: 'Returns the album and deleted (read back: the album no longer opens)' is garbled, and 'Shared albums are deleted or left in the app' is ambiguous rather than informative.

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?

Covers the facts an agent needs for a destructive single-param call: irreversibility, photo preservation, confirmation protocol, and post-delete verification. Return shape need not be explained since an output schema exists. The one gap is disambiguation from photos_album_remove and photos_delete.

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?

Single parameter with 100% schema coverage ('An album id from photos_albums'), so the schema does the work and the description needn't elaborate. The description adds nothing about the album_id beyond confirming the resource is album-scoped, which is the expected 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?

States a specific verb and resource ('Delete one of the person's own albums') with a clear scope qualifier ('own'). It implicitly separates itself from photos_delete (photo-level deletion) by noting photos stay in the library, but it never addresses the ambiguous relationship with the sibling photos_album_remove.

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?

Gives a real precondition — 'Ask the person first, naming the album and how many photos it holds' — which is valuable usage context for a destructive tool. However, it offers no guidance on when to pick this over photos_album_remove or photos_delete, so the core when-vs-alternatives question is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.