Skip to main content
Glama

SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_pgy_get_creator_fans_summary

Read-only

根据完整 user_id 获取小红书蒲公英创作者粉丝总数、平台增长指标、活跃、阅读和互动粉丝人数及占比。 查询粉丝规模和活跃情况时使用;年龄、性别、地域和兴趣等构成使用创作者粉丝画像工具。 不支持指定日期或统计周期;增长周期及各统计窗口截止日期未提供,不能按查询日期推算,不承诺指定期间增长数据。 成功直接返回汇总字段和 points;成功调用扣减 20 积分,失败不扣费。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYes小红书用户 ID。已有完整 user_id 时原样使用,否则从用户搜索、用户信息或笔记作者信息获取;不要传昵称、小红书号、主页链接或笔记 ID。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
user_idYes小红书用户 ID。已有完整 user_id 时原样使用,否则从用户搜索、用户信息或笔记作者信息获取;不要传昵称、小红书号、主页链接或笔记 ID。
follower_countYes蒲公英口径粉丝总数,单位人;未知时为 null
read_follower_ratioYes平台返回的阅读粉丝占比,0.001 表示 0.1%;保留平台精度,分母及统计周期未确认,不能沿用相邻人数字段的 28/30 天周期,不用返回人数复算;未知时为 null
follower_growth_rateYes平台返回的粉丝增长率,0.1 表示 10%;不是粉丝构成占比,不限于 0–1。统计周期和计算基数未明确,不用返回人数复算;未知时为 null
active_follower_ratioYes平台返回的活跃粉丝占比,0.419 表示 41.9%;保留平台精度,分母及统计周期未确认,不能沿用相邻人数字段的 28/30 天周期,不用返回人数复算;未知时为 null
follower_growth_countYes平台返回的粉丝增长数量;统计周期及是否扣除流失未明确,不可直接解释为近 30 天新增关注人数或净增人数;未知时为 null
engaged_follower_ratioYes平台返回的互动粉丝占比,0.1 表示 10%;保留平台精度,0 不表示互动人数一定为 0;分母及统计周期未确认,不能沿用相邻人数字段的 28/30 天周期,不用返回人数复算;未知时为 null
read_follower_count_30dYes平台 30 天统计窗口内的阅读粉丝数,单位人;截止日期未提供,不能按本次查询日期推算起止日期;不是阅读次数;活跃、阅读、互动人数不能假定互斥,不可相加作为总人数;未知时为 null
active_follower_count_28dYes平台 28 天统计窗口内的活跃粉丝数,单位人;截止日期未提供,不能按本次查询日期推算起止日期;活跃判定按平台口径,不等同阅读或互动人数;活跃、阅读、互动人数不能假定互斥,不可相加作为总人数;未知时为 null
engaged_follower_count_30dYes平台 30 天统计窗口内的互动粉丝数,单位人;截止日期未提供,不能按本次查询日期推算起止日期;不是互动次数,具体互动构成按平台口径;活跃、阅读、互动人数不能假定互斥,不可相加作为总人数;未知时为 null

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses cost behavior (成功调用扣减 20 积分,失败不扣费), the success return shape (汇总字段和 points), and a substantive data limitation (增长周期及统计窗口截止日期未提供,不能按查询日期推算). This is exactly the extra operational context annotations cannot carry.

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?

Front-loaded with purpose, then usage/alternative, then data limitations and billing. Every sentence carries signal, though the date/window disclaimer is lengthy and slightly repetitive (不支持指定日期 and 不能按查询日期推算 overlap).

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

Completeness5/5

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

An output schema exists so return values need not be detailed, and the readOnly/openWorld annotations cover the safety profile. With cost, alternative routing, and data-scope caveats all present, an agent has everything needed to call this 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 coverage is 100% for the single user_id parameter and it is fully documented in the schema (including format and anti-patterns). The description only reinforces that a complete user_id is required, adding minimal meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb (获取) and a well-enumerated resource set (粉丝总数、平台增长指标、活跃/阅读/互动粉丝人数及占比), and explicitly names the sibling it is not (粉丝画像工具). An agent can distinguish this from xhs_pgy_get_creator_fans_profile without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger (查询粉丝规模和活跃情况时使用) and routes the other case to a named alternative (年龄、性别、地域和兴趣等构成使用创作者粉丝画像工具). It also states exclusions (不支持指定日期或统计周期), leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources