Skip to main content
Glama

like_qzone

Likes a QQ Zone post using its tid from get_qzone_msg_list, requiring access or management permission for that post.

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": "like_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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the operation requires access or management rights on the specific post, which is an auth precondition the agent must satisfy before calling. It does not say what happens if the post is already liked or whether the call is idempotent.

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 compact sentence, front-loaded with the action and resource, followed by parameter provenance and the permission caveat; no filler. It is slightly dense for piling three clauses into one sentence, but every clause earns its place.

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 simple 3-parameter, single-required-parameter mutation with full schema coverage and annotations present, the description covers action, parameter source, and authorization. The notable remaining gap is the absence of any statement about repeat likes or failure behavior, and no differentiation from the public-feed like siblings, which matters given how many like tools share this namespace.

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 description coverage is 100%, including hints for abstime ("pass the real value for reliability") and target_uin ("omit to use the bot's own account"), so the schema does the heavy lifting. The description contributes only the origin of tid, which is useful routing information but does not add format or validity meaning beyond the schema. Baseline 3 is appropriate.

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?

The description gives a specific verb and resource ("给一条说说点赞", like a Qzone post) plus the product scope (QQ 空间), which distinguishes it from generic like tools. It also ties the operation to a concrete id source (tid 来自 get_qzone_msg_list). It stops short of explicitly contrasting with the sibling public-feed like tools, so it is clear but not fully differentiating.

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 provides real usage context: where the tid comes from (get_qzone_msg_list) and the prerequisite that the caller needs access or management permission on that post. What it does not state is when to choose this over the public-feed like siblings (set_qzone_public_like / set_qzone_public_comment_like); the choice is only implied by the message-list provenance.

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