Skip to main content
Glama

qzone_delete_album

Destructive

Deletes a personal Qzone album and all its photos using the album ID from your album list. Use it to remove an unwanted album and its contents from your QQ Zone.

Instructions

Delete one of your personal 空间相册 albums together with its 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>"
    },
    "name": "qzone_delete_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
album_idYesAlbum id from qzone_albums

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds genuinely new behavioral context: deletion cascades to all photos in the album, and the phrase 'your personal' signals an ownership constraint. It stops short of stating irreversibility or what happens on a partial failure.

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?

One sentence, front-loaded with the verb, with zero filler. The embedded untranslated term '空间相册' is slightly awkward but does not obscure meaning.

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 single-parameter destructive tool with rich annotations and no output schema, the description covers what gets removed and the cascade effect. Remaining gaps (permanence, permission requirements, failure behavior) are modest given the annotations already flag destructiveness.

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?

There is a single parameter with 100% schema coverage, and the schema already explains it is an album id sourced from qzone_albums. The description adds no format, type, or sourcing detail beyond that, so the baseline of 3 applies.

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 your personal ... albums') plus the cascade scope ('together with its photos'), which distinguishes it from qzone_delete_photos and qzone_album_photos without needing the schema. It does not explicitly name a sibling it is not, which keeps it short of a 5.

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: an agent can infer this is the tool for removing an album you own. There is no explicit when-to-use versus when-to-use-an-alternative guidance, and no stated prerequisite such as needing the album_id from qzone_albums first (that hint lives only in the schema).

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