Skip to main content
Glama

list_users

Read-onlyIdempotent

Fetch a paginated list of followers' OpenIDs from a WeChat Official Account. Pass the next_openid cursor from a previous response to retrieve the following page.

Instructions

分页获取关注者 OpenID。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
next_openidNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

注解已经覆盖了只读、幂等、非破坏等安全特征,描述额外补充了分页行为,这是有价值的信息。但它没有说明游标的语义、分页大小、排序方式或响应结构;不过输出 schema 已经存在,可以承担一部分说明义务。没有与注解矛盾。

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?

描述只有一句话,动作和资源对象前置,没有多余内容,结构高效。虽然信息量偏少,但作为简洁性评估,它没有浪费任何字符。

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?

对于首次无参数调用,描述加上注解和输出 schema 基本够用;但对于完整的分页迭代调用,缺少 next_openid 游标语义和与兄弟工具的选用规则。整体处于最低可用的水平,但还有明确缺口。

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

schema 对参数的描述覆盖率为 0%,描述必须补偿这一缺口,但描述完全没有解释 next_openid 的含义。虽然“分页”暗示该参数与分页有关,但 agent 无法确定它到底是游标、起始位置还是上一页最后一个 OpenID,这对后续翻页调用存在实际风险。

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?

描述明确说明操作为分页获取关注者 OpenID,动词和资源对象清晰。它与其他兄弟工具如 get_user_info(单个用户信息)、batch_get_user_info(批量用户信息)、get_user_ids_by_tag(按标签获取用户 ID)能够明显区分,不会产生歧义。

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?

从描述中可以推断该工具用于分页列出所有关注者的 OpenID,属于隐含用法。但没有明确说明何时使用它而非 get_user_ids_by_tag 或 batch_get_user_info,也没有给出任何排除条件或备选工具指引。

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.