Skip to main content
Glama

set_group_album_media_like

Mark a specific media item in a QQ group album as liked using group, album, and batch IDs obtained from the corresponding list tools.

Instructions

set_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": "set_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

B3.1/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, open-world call, and the description is consistent with that (a like action, not a deletion). It adds the concrete constraint that batch_id must be the decimal string of the actual batch, but says nothing about what happens on repeat calls, whether the like can be toggled, rate limits, or error behavior for a mutation tool.

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?

Very short and the critical batch_id format constraint is placed last but clearly stated. The opening repeats the tool name verbatim, and the sentence '替换群号及对应资源标识' is vague placeholder-like phrasing that consumes space without conveying specifics; the mixed Chinese/English is acceptable given the parameter naming.

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 4-parameter mutation tool with no output schema and sparse schema descriptions, the definition covers the essentials an agent needs to call it: where each ID comes from and the batch_id format. It is incomplete on return/response expectations, permissions, and repeat-call semantics, which matters for a write operation.

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 coverage is only 25% (only group_id is documented), so the description must compensate and does partially: it explains album_id's source, that lloc is an alternative identifier to the video id, and the decimal-string format required for batch_id. It still leaves the relationship between lloc and batch_id ambiguous — whether lloc is optional, required, or an alternative to another identifier — and doesn't clarify what 'replace group number and resource identifier' means operationally.

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

Purpose3/5

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

The description restates the tool name and then explains where the identifiers come from (album_id from get_group_album_list; lloc/video id and batch_id from get_group_album_media_list), which implies a like action on album media. However, it never states the effect in prose — no explicit 'marks media as liked' or how it differs from cancel_group_album_media_like — so the purpose must be inferred from the name plus parameter sourcing.

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?

There is useful workflow guidance in the form of ID provenance, telling the agent to obtain album_id and batch_id/lloc from the two read tools listed. It does not cover when to use this versus the cancel counterpart, nor any prerequisites, permission requirements, or idempotency/repeat-call behavior.

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