Skip to main content
Glama

set_qzone_public_follow

Follow or unfollow a recommended Qzone public feed author using the exact feed entry returned by get_qzone_public_feeds; set enable to true or false.

Instructions

蹲或取消蹲推荐动态作者 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 feed 需保留作者 cell_user_info。 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_follow"
  }
}

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

A3.6/5.0
Behavior3/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 mutation and open-world nature are covered structurally. The description adds useful context beyond them: the operation is an upstream relationship change and the result preserves unknown fields. It does not mention reversibility (unfollow undoing a follow), rate limits, or auth requirements, so it adds limited extra depth.

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?

The action is front-loaded in the first clause, followed by the provenance constraint and the return note. Dense and mostly waste-free, though the mixed Chinese/English phrasing and the interleaving of input-validation rules with return behavior slightly weaken scanability.

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?

Only two parameters, one required nested object, and full schema coverage, so the description carries little extra burden. It covers the critical failure mode (fabricated feed objects) and even summarizes the return value in the absence of an output schema; only error/edge behavior is unaddressed.

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%, so the baseline is 3: the schema already documents both feed and enable including defaults. The description reinforces the feed contract (verbatim entry, preserve author cell_user_info, replace all placeholder fields), but much of that overlaps the existing schema text rather than adding new meaning.

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 pair and resource: "蹲或取消蹲推荐动态作者" (follow/unfollow a recommended feed author), with the toggle behavior made explicit via the enable parameter. The resource (public follow relationships on Qzone recommended feeds) is distinct enough from the set_* siblings that an agent can identify it, though the description never names a sibling to contrast with.

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 hard prerequisite rather than a vague hint: the feed must be taken verbatim from get_qzone_public_feeds' feeds array and must not be synthesized from an old tid. It does not say when to use this versus other set_qzone_public_* tools or what happens if the feed is stale, so it stops short of full when/when-not guidance.

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