Skip to main content
Glama

SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_pgy_get_creator_fans_profile

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。
data_dateYes平台标注的数据日期(YYYY-MM-DD),不代表查询时间或统计起止范围;未知时为 null
age_distributionYes粉丝年龄分布;保留平台年龄区间标签,不推断端点含义;不保证完整,未知时为 null,明确为空时为 []
city_distributionYes平台返回的粉丝城市分布;不保证列出全部城市,不重新归一化或补其他;未知时为 null,明确为空时为 []
device_distributionYes粉丝设备品牌分布;不保证列出全部品牌,不重新归一化或补其他;未知时为 null,明确为空时为 []
gender_distributionYes粉丝性别分布;不推算缺失占比,未知时为 null
region_distributionYes粉丝地域分布;标签可包含省份、中国、海外等,不统一视为省份;不保证完整,未知时为 null,明确为空时为 []
interest_distributionYes粉丝兴趣分布;不保证分类完整或互斥,不用占比之和推算其他兴趣;未知时为 null,明确为空时为 []

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them: platform-default statistics range with no date override, distribution not guaranteed complete and not usable to derive follower counts, returns profile fields plus points, 20-credit deduction on success and no charge on failure. These cost and limitation disclosures are exactly the behavioral detail annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four tightly packed lines, front-loaded with purpose then routing, limitations, and billing. Every sentence carries distinct information with no filler.

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?

With annotations covering read-only/open-world behavior and an output schema present, the description supplies the remaining essentials: intended scope, sibling routing, statistical caveats, and credit cost. Nothing needed to invoke or interpret the call is 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?

Schema coverage is 100% and the single user_id parameter is fully documented in the schema (pattern, sourcing rules, prohibited inputs). The description adds only the '完整 user_id' emphasis, which largely restates the schema constraint, so baseline 3 is appropriate.

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 resource (获取小红书蒲公英创作者粉丝画像) and enumerates the exact dimensions returned (年龄、性别、地域、城市、兴趣、设备品牌及数据日期). It explicitly distinguishes itself from the fans-summary and creator-profile siblings, so an agent can route correctly without opening schemas.

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?

Explicitly states when to use it (查询粉丝构成时使用) and names the alternatives with their conditions: 粉丝规模、增长、活跃、阅读和互动 use the fans summary tool, and 创作者资料和报价 use the profile tool. Covers both when-to-use and when-not-to-use.

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