SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_pgy_get_creator_profile

Read-only

根据完整 user_id 获取小红书蒲公英创作者档案、粉丝和商业笔记规模、合作行业、笔记阅读与互动中位数、内容分类、特征标签和创作者图文/视频合作报价。查询蒲公英创作者资料和报价时使用；普通账号资料使用用户信息工具。笔记表现使用创作者笔记表现工具；粉丝画像使用创作者粉丝画像工具；指标随日期变化使用创作者指标趋势工具。图文和视频报价单位为人民币元；零值不表示免费合作。成功返回档案字段和 points；成功调用扣减 20 积分，失败不扣费。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	Yes	小红书用户 ID。已有完整 user_id 时原样使用，否则从用户搜索、用户信息或笔记作者信息获取；不要传昵称、小红书号、主页链接或笔记 ID。

Output Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	创作者昵称；上游未提供时为 null
`gender`	Yes	创作者性别：male 表示男，female 表示女；无法确认时为 null
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`red_id`	Yes	公开小红书号；缺失时为空字符串，不能作为 user_id 使用
`user_id`	Yes	小红书用户 ID。已有完整 user_id 时原样使用，否则从用户搜索、用户信息或笔记作者信息获取；不要传昵称、小红书号、主页链接或笔记 ID。
`location`	Yes	创作者资料所在地，不是 IP 属地；缺失时为 null
`avatar_url`	Yes	头像地址；缺失时为 null
`profile_url`	Yes	由 user_id 生成的用户主页地址
`video_price`	Yes	创作者视频笔记合作报价，单位：人民币元；未知时为 null，零值不表示免费合作
`feature_tags`	Yes	创作者特征标签；不是主页标签；未知时为 null，明确为空时为 []
`picture_price`	Yes	创作者图文笔记合作报价，单位：人民币元；未知时为 null，零值不表示免费合作
`follower_count`	Yes	蒲公英口径粉丝数，单位人；未知时为 null
`note_read_median`	Yes	蒲公英口径笔记阅读数中位数；未知时为 null
`content_categories`	Yes	内容分类；未知时为 null，明确为空时为 []
`business_note_count`	Yes	商业笔记数；未知时为 null
`cooperation_industries`	Yes	合作行业名称列表；未知时为 null，明确为空时为 []
`note_interaction_median`	Yes	蒲公英口径笔记互动数中位数；具体互动构成以上游口径为准；未知时为 null
`cooperation_note_count_30d`	Yes	近 30 天合作笔记数；未知时为 null
`received_like_and_collect_count`	Yes	获赞与收藏合计；不能拆算为独立点赞数或收藏数；未知时为 null

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 24, 2026

changedOutput schema / properties / gender / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "male",
+      "female"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / gender / description

Previous value: -"创作者性别文本；缺失时为 null"New value: +"创作者性别：male 表示男，female 表示女；无法确认时为 null"

addedOutput schema / properties / name / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / name / description

Previous value: -"创作者昵称"New value: +"创作者昵称；上游未提供时为 null"

removedOutput schema / properties / name / type
```
Removed value: -"string"
```

changedOutput schema / properties / picture_price / description

Previous value: -"图文笔记报价，单位：人民币元；未知时为 null，零值不表示免费合作"New value: +"创作者图文笔记合作报价，单位：人民币元；未知时为 null，零值不表示免费合作"

changedOutput schema / properties / video_price / description

Previous value: -"视频笔记报价，单位：人民币元；未知时为 null，零值不表示免费合作"New value: +"创作者视频笔记合作报价，单位：人民币元；未知时为 null，零值不表示免费合作"

AddedSep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover readOnlyHint/openWorldHint; the description adds non-obvious behavior — a 20-credit charge on success with no charge on failure, RMB-denominated quote units, and the caveat that a zero value does not mean free collaboration. These are exactly the operational facts annotations cannot express.

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?

Field list, routing rules, and caveats are front-loaded and each sentence carries information; it is dense but no sentence is filler. Slightly long for a single-parameter tool, keeping it from a 5.

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 fields need no elaboration, and the description still confirms success returns profile fields and points. With cost, units, and sibling routing all covered, an agent has 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% and the pattern/format guidance is already in the schema, so the baseline is 3. The description reinforces that a complete user_id is required but adds no syntax beyond what the schema states.

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 payload: 粉丝与商业笔记规模、合作行业、阅读与互动中位数、内容分类、特征标签、图文/视频报价. An agent can distinguish this from xhs_get_user_info_by_user_id purely from the text.

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 routes the agent: use this for PGY creator profiles and quotes, use user-info tools for ordinary accounts, and names four siblings (笔记表现、粉丝画像、指标趋势) with the condition that selects each. Nothing is left to inference.

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

All SocialDataX 小红书 Xiaohongshu XHS RedNote MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?