Skip to main content
Glama

get_qzone_msg_list

Read-only

Fetches a paginated list of QQ Zone posts from the current account by default, or from a specified QQ number when access is allowed.

Instructions

获取 QQ 空间说说列表(默认机器人自己的空间) 默认读取当前账号;指定 target_uin 时需有访问权限。 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_msg_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
numNo本页数量
posNo起始偏移
target_uinNo目标 QQ 号,省略则取机器人自己

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint=false, so the safety profile is covered. The description adds real behavior: the default target is the bot's own space and cross-account reads carry a permission prerequisite. It does not describe failure behavior when permission is missing, but that is a modest gap given annotation coverage.

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?

Compact and front-loaded: scope/default first, permission caveat second, return shape last. No redundancy or filler, though the knapsack could more cleanly separate the Chinese description from the English 'Returns:' line.

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?

No output schema exists, but the description compensates by stating the return is an object containing total count plus the current page's array. Combined with fully documented parameters and annotations, an agent has essentially everything needed to call it correctly.

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% (num, pos, target_uin all documented, including target_uin's default), so the schema does the heavy lifting and the baseline applies. The description's only genuine addition is the permission requirement tied to target_uin, which is framed more as usage guidance than parameter semantics.

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 ('获取 QQ 空间说说列表') and immediately qualifies the default scope (the bot's own space). It does not, however, distinguish itself from plausible siblings such as get_qzone_feeds or get_qzone_home_feeds, so an agent still has to infer which listing tool is right.

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?

Gives clear operating context: reads the current account by default, and reading another user's space via target_uin requires access permission. It stops short of naming an alternative tool or an explicit when-not-to-use condition.

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