Skip to main content
Glama

cancel_group_album_media_like

Destructive

Cancels a like on a specific media item in a QQ group album using group, album, and batch identifiers, letting you undo an accidental or unwanted like.

Instructions

cancel_group_album_media_like album_id 来自 get_group_album_list;lloc 或视频 id、batch_id 来自 get_group_album_media_list。替换群号及对应资源标识。 batch_id 必须是实际批次的十进制字符串。

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": {
      "group_id": "<group_id>",
      "album_id": "<album_id>",
      "batch_id": "<batch_id>"
    },
    "name": "cancel_group_album_media_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
llocNo
album_idYes
batch_idYes
group_idYes群号

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the mutation/risk profile is covered structurally. The description adds nothing beyond that: it does not say what is destroyed or reverted, whether the like must currently exist, whether the call is idempotent, or what errors occur for an invalid batch. The one behavioral note (batch_id must be a real batch's decimal string) is really a parameter constraint.

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?

Two short sentences with no filler, and the most important constraint (batch_id must be a real batch's decimal string) is placed at the end where it is easy to miss but still present. The leading repetition of the tool name is wasted space that could have been spent on stating the action.

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?

For a destructive, open-world mutation with no output schema and low schema coverage, the description covers parameter sourcing and the batch_id format but omits outcome behavior, permission requirements, and failure modes. It is adequate to construct a call but not to predict its effect.

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 description coverage is only 25% (only group_id is annotated, as 群号), so the description must compensate, and it largely does: it maps album_id to get_group_album_list, lloc/video id and batch_id to get_group_album_media_list, and warns that batch_id must be the decimal string of an actual batch rather than an index or name. That is meaningful disambiguation an agent could not get from the schema. It still leaves the lloc vs. video-id exclusivity rule implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens by restating the tool name verbatim rather than stating what the operation does (cancel a like on a group album media item). It never says what the action achieves or what state changes, leaving the name itself and the annotations to carry the meaning. The only added content is parameter provenance, so this is close to tautology.

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?

Implicit usage guidance exists: it tells the agent that album_id must be obtained from get_group_album_list and lloc/video id plus batch_id from get_group_album_media_list, establishing a required discovery chain before calling. However, there is no explicit when-to-use vs. when-not guidance and no differentiation from the sibling set_group_album_media_like, so the agent must infer that this is the inverse operation.

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