Skip to main content
Glama

get_qzone_public_feeds

Read-only

Reads Qzone public recommended feeds with cursor-based pagination; pass the previous next_cursor to fetch the next page for the same account and stop when has_more is false.

Instructions

读取空友爱看推荐动态,支持独立游标分页 cursor 原样使用上次返回的 next_cursor,仅适用于同一账号;has_more=false 时停止。 Returns: 推荐动态原始 cell 对象及分页状态,保留其余上游页面字段。

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_public_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo上次返回的 next_cursor,省略则刷新首页
include_htmlNoAlso return each feed item's raw HTML (large)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this as read-only, open-world, and non-destructive. The description adds useful behavior beyond that: cursor pagination must reuse the prior next_cursor verbatim, cursors are only valid for the same account, and iteration stops at has_more=false. It also notes the return shape, though it does not cover rate limits or authentication details.

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 definition is front-loaded with the tool's purpose, then gives pagination constraints and return information. It is compact and free of obvious padding, though the mixed Chinese/English and trailing upstream-fields note are slightly less polished.

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?

For a two-parameter read-only listing tool with no output schema, the description provides enough to call it correctly: purpose, cursor lifecycle, account constraint, stop condition, and return shape. Only explicit sibling differentiation and authentication expectations are missing.

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?

The input schema already has 100% description coverage for both cursor and include_html. The description reinforces cursor opacity and same-account validity, but mostly repeats schema semantics and does not mention include_html, so it adds only modest value beyond the structured schema.

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 feeds (推荐动态). It is clear what the tool returns, but it does not explicitly distinguish this from sibling feed tools such as get_qzone_home_feeds or get_qzone_feeds.

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 operational guidance for cursor pagination, same-account use, and stopping when has_more=false. However, it does not say when to choose this tool over sibling feed-listing tools, so alternative routing is left to inference.

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