Skip to main content
Glama

unlike_qzone

Removes a like from a QQ Zone post using its tid, with optional posting time and owner QQ number for accurate targeting.

Instructions

取消对一条说说的点赞(QQ 空间;取消赞端点待真机核实) tid 来自 get_qzone_msg_list;操作需有该说说的访问或管理权限。

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": {
      "tid": "<tid>"
    },
    "name": "unlike_qzone"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid
abstimeNo说说发表时间(unix 秒),传真实值更可靠
target_uinNo说说所属 QQ 号,省略则为机器人自己

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description does not contradict them: 'unlike' is a mutation but not a destructive one. Beyond the annotations it adds two pieces of genuine context — the permission requirement on the target post and the caveat that the unlike endpoint is still pending real-device verification, which warns the agent the call may not be reliable. It does not cover idempotency (unliking an unliked post) or failure behavior.

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?

A single dense sentence with the action front-loaded and the operational caveats trailing, with no filler. The parenthetical '取消赞端点待真机核实' is slightly buried for a caveat of that importance, but every clause carries information.

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 3-parameter mutation with annotations but no output schema, the description covers the essentials: what it does, where the key input comes from, the permission prerequisite, and an endpoint-reliability caveat. Return shape is not described, which is acceptable given no output schema is expected to be self-evident, though idempotency remains unaddressed.

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 100%, so the baseline would be 3; the description earns one more by stating the provenance of the required tid (get_qzone_msg_list), which the schema does not say. It adds nothing for abstime or target_uin, but those are already documented in the schema, including the default-to-self behavior for target_uin.

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 ('取消对一条说说的点赞') scoped to QQ 空间, which cleanly marks it as the inverse of like_qzone without needing to name it. It also names where the required tid originates (get_qzone_msg_list), so the agent knows the prerequisite call. It stops short of an explicit sibling contrast, which keeps it from 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?

It supplies a real usage precondition — the caller needs access or management permission on the target post — and tells the agent to obtain tid from get_qzone_msg_list first. It does not say when to prefer this over like_qzone or how to recover if the post is not already liked, so guidance is implied rather than explicit.

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