Skip to main content
Glama

set_qzone_public_upvote

Toggles or cancels an independent upvote on a QQ Zone public feed item using a feed object from get_qzone_public_feeds, separate from regular likes.

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_upvote"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, open-world mutation, so the baseline is covered. The description adds genuine behavior: the push is independent of normal likes, it can be reversed via enable=false, and the response is the upstream result with unknown fields preserved. It stops short of stating permission/rate-limit 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.

Conciseness5/5

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

Front-loads the action and its distinction from normal likes, then the hard input constraint, then the return note. Every clause carries an actionable constraint; nothing is padding.

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?

With only two parameters, a nested free-form feed object, and no output schema, the definition covers the essentials: valid input source, direction flag, and the shape of the return. Missing only prerequisite/permission context for an open-world mutation, which the annotations only partially signal.

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 is 3, but the description adds real meaning: the feed object must be the complete entry from get_qzone_public_feeds with original cell fields retained, and cannot be reconstructed from a tid. That constraint is not visible in the schema text.

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

Purpose5/5

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

Names a specific verb pair (推/取消推) and the resource (空友爱看动态), and explicitly marks it as 独立于普通赞, which separates it from the sibling set_qzone_public_like. An agent can select this tool without opening any schema.

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?

Gives a concrete precondition: the feed must be taken verbatim from the feeds array of get_qzone_public_feeds and must not be synthesized from an old tid, plus a warning that placeholder fields from examples must be fully replaced. It does not state whether a capability check (get_qzone_public_capabilities) or any permission is a prerequisite, and gives no explicit 'do not use when' case.

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