Skip to main content
Glama

get_qzone_feeds

Read-only

Retrieve QQ Zone friend feeds with structured post content, images, stats, and cursor-based pagination; optionally include raw HTML for each feed item.

Instructions

获取 QQ 空间好友动态,支持结构化正文与游标分页 保留 html;content/images 为可提取的正文和图片,未知值为 null。续页使用 next_cursor。 Returns: 好友动态、可提取的正文与图片、统计值及下一页游标;未知内容或统计为 null,HTML 保留。

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

Input Schema

NameRequiredDescriptionDefault
countNo本页数量
cursorNo上一次返回的 next_cursor;原样传递,省略 page_num 或传入对应页码
page_numNo页码(1 起);不传 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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: unknown content/stats are returned as null, content/images are extractable fields, and raw HTML is retained only when requested — useful since there is no output schema.

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?

Purpose is front-loaded, but the definition says the same thing twice: a Chinese prose block followed by a 'Returns:' line restating 正文/图片/统计/游标/null/HTML. The duplication costs roughly half the text without adding 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?

With four fully documented optional parameters, annotations carrying the safety profile, and no output schema, the description covers what matters: return contents, null semantics, HTML handling, and pagination continuation. The main remaining gap is that it never situates itself among the home/public feed siblings.

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 description coverage is 100%, so count/cursor/page_num/include_html are already documented in the schema. The description's '保留 html' hint loosely maps to include_html and the cursor note repeats schema text, adding little beyond baseline.

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?

States a specific verb+resource: fetching QQ Zone friend feeds (好友动态), with structured body and cursor pagination. The scope word 好友 distinguishes it in spirit from home/public feed siblings, but it never names those alternatives, so differentiation is left implicit.

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?

The only usage guidance is pagination-related (续页使用 next_cursor), which tells the agent how to continue but not when to choose this tool over get_qzone_home_feeds or get_qzone_public_feeds. No when-not conditions or prerequisites are given.

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