Skip to main content
Glama

qzone_delete_photos

Destructive

Deletes selected photos from a QQ Zone album using an album ID and photo IDs retrieved from qzone_album_photos.

Instructions

Delete photos from one of your 空间相册 albums (photo ids from qzone_album_photos).

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>",
      "photo_ids": "<photo_ids>"
    },
    "name": "qzone_delete_photos"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idYesAlbum id
photo_idsYesPhoto ids (lloc)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and the description is consistent with them. Beyond that it adds only the album scoping and id-source hint; it does not say whether deletion is permanent, whether it can be undone, or whether permissions/ownership restrictions apply, which matters for a destructive multi-item delete.

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 front-loaded sentence with the destructive action first and the id-source parenthetical second. No filler, no repetition of the tool name, nothing to trim.

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 two-parameter delete tool with full schema coverage, explicit destructive annotations, and no output schema, this covers the essentials an agent needs to call it. The only meaningful gap is the absence of any permanence/undo or permission statement for a destructive operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real meaning by telling the agent where photo_ids originate (qzone_album_photos), which the schema's terse 'Photo ids (lloc)' does not convey. It does not clarify whether album_id must be the owning album of those ids or what happens with ids from another album.

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 (Delete) and resource (photos in an album), scoped to 'one of your albums', which separates it from sibling tools like qzone_delete_album or qzone_board_delete. It also names the source of the photo ids, giving an agent enough to identify the operation without opening the schema.

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?

Provides a concrete prerequisite/workflow pointer: photo ids must come from qzone_album_photos, which effectively routes the agent through a read step before this destructive call. It stops short of stating when *not* to use it (e.g., removing a whole album vs individual photos is only implied).

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

Deploy Server

Other Tools