Skip to main content
Glama

get_qzone_msg_detail

Read-only

Retrieve QQ Zone post details and a page of top-level comments, including server-inline replies, using a tid from the message list; access or management permission is required.

Instructions

获取 QQ 空间说说详情与一页评论(含服务端内联回复,需有访问权限) tid 来自 get_qzone_msg_list;操作需有该说说的访问或管理权限。 replies 仅为服务端内联回复,不保证完整。 Returns: 说说详情、服务端报告的评论总数与本页评论;replies 仅含服务端内联返回的二级回复,不保证完整。

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>"
    },
    "name": "get_qzone_msg_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
numNo请求的一级评论数量,实际数量受服务端限制
posNo一级评论起始偏移
tidYes说说 tid(来自 get_qzone_msg_list / send_qzone_msg)
target_uinNo说说所属 QQ 号,省略则取机器人自己

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a safe read (readOnlyHint=true, destructiveHint=false), and the description adds real behavioral context beyond them: a permission requirement, the provenance of the tid, and the caveat that replies are only server-inline and not guaranteed complete. It does not discuss pagination limits or server-side caps on counts, which keeps it short of 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.

Conciseness3/5

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

The permission and tid-origin constraints are front-loaded, which is good, but the text repeats itself: the 'replies are only server-inline and not guaranteed complete' caveat appears twice, and the Returns section restates the opening sentence. Roughly a third of the text is redundant.

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 no output schema, the description usefully enumerates what comes back (post detail, server-reported total comment count, this page of comments, inline replies) and flags the partial-reply caveat plus the access requirement. It is essentially complete for callers, missing only guidance on paging until the total is exhausted.

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 description coverage is 100%, so num, pos, tid and target_uin are all documented in the schema itself, including defaults, bounds and tid provenance. The description adds little parameter-level meaning beyond reiterating the tid source, so the baseline 3 applies.

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 and resource (fetch Qzone post detail plus one page of comments), names the input's origin (tid from get_qzone_msg_list), and distinguishes itself from the list-oriented sibling. An agent can tell this is the single-post detail reader without opening the schema.

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

Usage Guidelines3/5

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

Provides useful prerequisites: the tid must come from get_qzone_msg_list and the caller needs access/management permission on that post. However, it never routes to comment-only or reply-only siblings (e.g. get_qzone_public_comments / get_qzone_public_replies), so when-to-use-this-vs-another remains implied rather than stated.

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