Skip to main content
Glama

set_qzone_public_like

Likes or unlikes a QQ Zone public feed using the complete feed entry from get_qzone_public_feeds; set enable to false to remove the like.

Instructions

点赞或取消赞推荐动态 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 Returns: 上游普通赞操作结果,保留未知字段。

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": {
      "feed": "<feed>"
    },
    "name": "set_qzone_public_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesget_qzone_public_feeds 返回的完整 feeds 条目,保留所有原始 cell 字段
enableNotrue 点赞,false 取消赞

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=false, destructive=false, openWorld=true), and the description adds useful context beyond them: that `enable=false` reverses a like, that the payload must be preserved intact, and that the return value is the upstream like result with unknown fields retained. It doesn't discuss idempotency of repeated likes or failure modes, which keeps it from a 5.

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 sentences, front-loaded with the action and the data-provenance constraint, followed by the return contract. The clause-dense Chinese phrasing and semicolon chaining are slightly run-on, but every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter mutation with no output schema, the description covers the action, the direction flag, the required provenance of the feed object, and what the call returns. Nothing an agent needs in order to invoke it correctly is missing.

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 coverage is 100%, so the baseline would be 3, but the description adds real meaning: it warns against synthesizing the `feed` object and states that placeholder fields in examples must be wholly replaced, which is a practical failure mode the schema alone doesn't prevent. The `enable` semantics are already in the schema, so part of the text is reinforcement rather than new information.

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 opens with a specific verb pair plus resource ('点赞或取消赞推荐动态'), which tells an agent exactly what operation it performs and that the `enable` flag selects direction. It also names the sibling `get_qzone_public_feeds` as the data source, though it does not explicitly distinguish itself from other like-style siblings such as `like_qzone` or `set_qzone_public_upvote`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a hard precondition: the feed object must come verbatim from the `feeds` array of `get_qzone_public_feeds`, and must not be constructed from an old tid. That is clear when-to-use and a strong when-not-to-do-X constraint. It stops short of naming a competing tool for the case where the target is not a public feed.

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