Skip to main content
Glama

get_qzone_public_comments

Read-only

Fetches the next page of comments for a QZone public feed using the original feed entry and cursor value returned by a prior detail or comments response.

Instructions

继续读取推荐动态评论 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 先读详情获取初始评论及 attach_info,再原样传入 cursor。 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>",
      "cursor": "<cursor>"
    },
    "name": "get_qzone_public_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesget_qzone_public_feeds 返回的完整 feeds 条目,保留所有原始 cell 字段
cursorYes详情或上一评论页返回的 attach_info

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the safety bar is low. The description adds real behavioral context: the feed object must be passed through verbatim from get_qzone_public_feeds, and the return preserves comments, pagination and unknown fields from the upstream page. It does not mention rate limits or failure modes, but for a read-only pagination call this is adequate.

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 key constraint, then the ordering instruction, then the return shape; three sentences with little waste. The note about replacing placeholder fields in examples is slightly meta but useful for avoiding a common misuse.

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 100% schema coverage and clear annotations, the description only needs to carry the provenance rule, the ordering, and the return shape — all of which it does. There is no output schema, and the description compensates by stating that the upstream comment page object is returned intact.

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. The description goes beyond the schema by specifying the provenance rule for 'feed' — it must be the complete entry from get_qzone_public_feeds and must not be reconstructed from an old tid — which the schema does not state. The cursor guidance largely restates the schema's 'attach_info' description.

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 states a specific operation — continuing to read the comment feed of a recommended feed ('继续读取推荐动态评论 feed') — and names the source tool for the feed object. It is clearly distinct from get_qzone_public_feed_detail, which it positions as the first-page entry point, though the phrasing is terse and assumes familiarity with the 'attach_info' concept.

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 gives explicit sequencing: first read the detail to obtain initial comments and attach_info, then pass that cursor here to continue. It also rules out one wrong approach (fabricating with an old tid). What it does not say explicitly is that this tool is not for the first page, but that is strongly implied by '继续读取' and the scroll workflow.

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