Skip to main content
Glama

set_qzone_msg_right

Change the viewing permission of a published Qzone post by tid to control who can see it. Requires post access and a valid ugc_right value (1, 4, 16, 64, or 128).

Instructions

修改一条已发说说的查看权限(QQ 空间,按 tid) tid 来自 get_qzone_msg_list;操作需有该说说的访问或管理权限。 16 表示仅所选好友可见。 Rules: ugc_right must be one of 1, 4, 16, 64, 128; target_uins is required when ugc_right is 16 or 128. 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": {
      "tid": "<tid>",
      "ugc_right": "<ugc_right>"
    },
    "name": "set_qzone_msg_right"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes说说 tid(来自 get_qzone_msg_list / send_qzone_msg)
ugc_rightYes查看权限:1=所有人可见,4=好友可见,16=部分好友可见,64=仅自己可见,128=部分好友不可见
target_uinsNo权限作用 QQ 号数组;ugc_right=16 时表示可见名单,128 时表示不可见名单

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 readOnlyHint=false, openWorldHint=true, destructiveHint=false, and the description is consistent with a mutating, non-destructive operation. It adds the authorisation requirement (access or management rights on the post) and the return value ('updated permission object'), though it does not say what failure looks like when permission is missing.

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?

Front-loaded with the verb and resource, then tid provenance, permission precondition, value rules, and return value in three compact sentences. The clause '16 表示仅所选好友可见' duplicates the schema's ugc_right description and is the one bit of avoidable repetition.

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 three-parameter mutation with full schema coverage and existing annotations, the description covers provenance, permission precondition, valid values, the conditional target_uins requirement, and the return value in lieu of an output schema. Nothing an agent needs 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 baseline is 3, but the description adds a cross-parameter constraint the schema does not enforce: target_uins is required when ugc_right is 16 or 128, and the allowed value set 1/4/16/64/128. That is genuine meaning beyond the schema's per-field prose.

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?

States a specific verb + resource + scope: modify the view permission of an already-published QZone post, addressed by tid. It also pins the identifier's origin (tid comes from get_qzone_msg_list), which distinguishes it from sibling mutators like delete_qzone_msg and send_qzone_msg.

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 clear preconditions: the tid must come from get_qzone_msg_list, and the caller needs access or management permission on that post. It stops short of naming alternatives or saying when not to use this tool (e.g., use a profile-level permission setter for global settings), so it is clear context but not full routing 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