Skip to main content
Glama

get_qzone_home_feeds

Read-only

Read Qzone home feed posts for the current or a specified permitted account, returning complete share details and pagination cursors.

Instructions

读取自己或有权访问的空间主页动态,保留完整分享信息 Returns: 完整动态及分页状态;访问受空间权限限制,旧说说接口保持不变。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_qzone_home_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo上次返回的 next_cursor,仅限同一账号及主页
target_uinNo主页所属 QQ 号,省略则为当前账号
include_htmlNoAlso return each feed item's raw HTML (large)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the agent knows this is a safe read. The description adds meaningful behavior: results are gated by space permission, pagination state is returned, and full share payloads are preserved. It does not describe rate limits, pagination size, or ordering, so it adds some value but not rich disclosure.

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 definition is short and front-loads the purpose, which is good. The final clause about the legacy mood interface sits awkwardly after the return-value statement, and its relevance to the agent is unclear, so it weakens an otherwise compact structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of stating the return shape, and it does so only briefly ('完整动态及分页状态'). The permission caveat is useful for a read-only, open-world tool. The note about the legacy interface is not enough to be complete, and ordering and size constraints remain unstated.

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% and all three parameters carry their own explanations, including the cursor being scoped to the same account and home page. The description mentions pagination state but adds no syntax, range, or interaction detail beyond the schema. The baseline of 3 is therefore appropriate.

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 names a specific verb and resource: reading Qzone home feeds that belong to the caller or to a space the caller has permission to access, while preserving complete share information. This is more specific than a title restatement. However, it does not explicitly differentiate itself from the closely named sibling get_qzone_feeds, and the trailing remark about the legacy mood interface is too vague to help with differentiation.

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?

It gives some context for use by qualifying the caller's own space or an accessible space and noting that access is limited by space permissions. It gives no explicit when-to-use or when-not-to-use guidance against get_qzone_feeds, get_qzone_public_feeds, or get_qzone_feed_detail. The phrase '旧说说接口保持不变' hints at a boundary with a legacy interface but never names it clearly.

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