Skip to main content
Glama

get_qzone_public_feed_detail

Read-only

Retrieve details and initial comments for a QQ Zone public feed using a feed item returned by get_qzone_public_feeds; use its attach_info to continue comment pagination.

Instructions

读取推荐动态详情及初始评论 feed 必须原样取自 get_qzone_public_feeds 的 feeds 数组,不能用旧说说 tid 拼造;示例中的占位字段须整体替换。 Returns: 上游详情 data;初始评论位于 feed.feed.cell_comment.comments,续页使用 attach_info。

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": "get_qzone_public_feed_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedYesget_qzone_public_feeds 返回的完整 feeds 条目,保留所有原始 cell 字段
include_htmlNoAlso return each feed item's raw HTML (large)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds genuinely new behavioral detail: where the initial comments live (feed.feed.cell_comment.comments) and that continuation pages use attach_info. It stops short of describing limits, but the added context is meaningful.

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?

It is compact and front-loaded: purpose first, then the source constraint on feed, then the return shape and pagination path. Every clause carries actionable information, and none of it repeats the annotations.

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?

There is no output schema, and the description compensates by naming the returned upstream detail data and the exact path to initial comments plus the attach_info continuation mechanism. Combined with the verbatim-feed rule for the required nested parameter, an agent has everything needed to call it correctly on the first attempt.

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 would be 3, and the description does add meaning on top: it forbids constructing the feed object from a tid, demands verbatim reuse of the upstream entry, and warns that example placeholders must be wholly replaced. Those constraints clarify correct usage of the nested feed parameter beyond the schema text.

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 verb and resource: reading recommended-feed (推荐动态) detail together with its initial comments. It also names the upstream sibling get_qzone_public_feeds as the sole source of the feed, which helps distinguish it from the generic get_qzone_feed_detail, though it never explicitly contrasts the two.

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 a concrete precondition and a prohibition: the feed must be copied verbatim from the feeds array of get_qzone_public_feeds and must not be fabricated from an old 说说 tid, plus placeholder fields in examples must be fully replaced. That is clear when/how guidance, but there is no explicit exclusion telling the agent when to prefer get_qzone_feed_detail or get_qzone_public_comments instead.

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