Skip to main content
Glama

get_qzone_feed_detail

Read-only

Read a complete QQ Zone feed post by its 24-character hex tid to generate share cards or pass feed data to share-ark.

Instructions

按说说 tid 读取完整空间动态,可用于生成分享卡片 将示例 tid 替换为 get_qzone_msg_list 或 send_qzone_msg 返回的 24 位十六进制说说编号。把结果的 feed 原样传给 get_qzone_share_ark;读取和分享均受空间权限限制。 Rules: tid must be a 24-character hexadecimal post ID. Returns: 完整动态及上游详情字段。feed 保留图片、视频、分享信息和未知字段,可直接用于 get_qzone_share_ark;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": {
      "tid": "<tid>"
    },
    "name": "get_qzone_feed_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
tidYes24 位十六进制说说编号
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.1/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world profile, and the description adds real context beyond them: access is gated by Qzone permissions, attach_info carries an upstream comment cursor and does not auto-paginate, and unknown fields in feed are preserved. That last part is important because it tells the agent the feed can be forwarded as-is without data loss.

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 description is split into purpose, rules, returns and caveats, with the primary action front-loaded. Some phrasing is operational scaffolding rather than tool semantics (the instruction to replace the example tid), but overall it stays short and each block carries information.

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?

There is no output schema, and the description does a reasonable job of explaining the return shape (feed plus upstream detail fields, attach_info as a comment cursor). For a read tool with annotated safety and only two parameters, the key gaps are minor: the effect of include_html and the meaning of upstream detail fields are left implicit.

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 both tid and include_html are already documented, and the description's tid format rule largely repeats the schema. The include_html flag, which materially changes response size by returning raw HTML, is never mentioned in the description, so there are no extra semantics beyond the schema.

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?

The first clause states a specific verb and resource: read the complete Qzone feed by post tid, and it adds the concrete downstream use (generating a share card). It names the siblings that supply the tid and the sibling that consumes the result, so an agent can place it in a workflow without opening another schema.

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 tells the agent where the tid comes from (get_qzone_msg_list or send_qzone_msg output) and what to do with the result (pass feed unchanged to get_qzone_share_ark). It does not explicitly say when to choose this over near-name siblings such as get_qzone_msg_detail, but the input/output routing is clear and actionable.

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