Skip to main content
Glama

set_qzone_public_comment_like

Likes or unlikes comments and replies on Qzone public feed posts by using the original feed and comment objects returned by the feed APIs.

Instructions

点赞或取消赞推荐动态中的评论或回复 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 comment 可取 get_qzone_public_feed_detail 返回的 feed.feed.cell_comment.comments,或后续评论页;保留完整对象。 必须保留评论原始 like.id。 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>",
      "comment": "<comment>"
    },
    "name": "set_qzone_public_comment_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesget_qzone_public_feeds 返回的完整 feeds 条目,保留所有原始 cell 字段
replyNo评论或回复页返回的完整回复对象,保留 user 等原始字段
enableNotrue 点赞,false 取消赞
commentYes详情或评论页返回的完整评论对象,保留 user 等原始字段

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the write nature and external reach are known. The description adds valuable behavioral context beyond annotations: objects must be passed through unmodified from upstream calls, unknown fields must be preserved, and the original like.id must be kept intact, indicating an idempotent toggle keyed on upstream identifiers. It also notes the return is the upstream like result with unknown fields retained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely dense for its length: three short clauses cover data provenance, object integrity, and return shape, with no filler. The critical constraint about not fabricating a tid from old 说说 is front-loaded in the first sentence.

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 mutation tool with nested object parameters and no output schema, the description covers provenance and field preservation well but leaves gaps: it doesn't state what happens on partial failure, whether enable=false requires the same comment object, or how pagination of comment pages should be handled when the target isn't on the first page.

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 100% and every parameter (feed, comment, reply, enable) already has a description, so the schema carries most of the burden. The description adds meaning for feed and comment provenance and the enable true/false semantics, but says nothing meaningful about the reply parameter that isn't already in the schema.

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 specific verbs (点赞或取消赞) and a precise resource (推荐动态中的评论或回复), and the enable parameter disambiguates like vs unlike. It distinguishes itself from set_qzone_public_like by scoping to comments/replies, and from comment_qzone_public_feed by being a like action rather than a post action.

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 clearly says the feed must be taken verbatim from get_qzone_public_feeds and the comment must come from get_qzone_public_feed_detail (or a later comment page), which routes the agent to the right prerequisite calls. What's missing is an explicit statement of when to prefer this over set_qzone_public_like or how to obtain a reply-page object beyond the vague mention of 后续评论页.

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