SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_user_info_by_user_id

Read-only

根据 user_id 获取单个小红书用户信息。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`user_id`	Yes	小红书用户 user_id。用户已提供时原样使用；否则可从笔记搜索、商品评价、商品评价回复、笔记详情、标签页笔记列表、用户信息或用户发帖列表结果中的 user_id/author.user_id 复制；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称。

Output Schema

TableJSON Schema

Name	Required	Description
`bio`	Yes	用户个人简介（biography）；没有简介时为空字符串
`name`	Yes	用户名称
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`red_id`	Yes	用户公开小红书号；没有小红书号时为空字符串
`user_id`	Yes	用户 user_id
`verified`	Yes	是否已认证
`avatar_url`	Yes	用户头像链接；没有头像链接时为 null
`ip_location`	Yes	用户 IP 属地；没有 IP 属地时为空字符串
`profile_url`	Yes	用户主页链接；没有主页链接时为 null
`profile_tags`	Yes	主页头部标签名称列表；没有标签时为空数组
`follower_count`	Yes	粉丝数
`following_count`	Yes	关注数
`posted_note_count`	Yes	已发布笔记数
`verification_name`	Yes	认证主体名称；没有认证主体时为空字符串
`received_like_count`	Yes	用户内容累计收到的点赞数
`is_enterprise_account`	Yes	是否为企业账号
`verification_category`	Yes	认证补充信息；可能是行业类目或认证主体名称；未认证或没有认证信息时为空字符串
`received_collect_count`	Yes	用户内容累计被收藏数
`is_professional_account`	Yes	是否为专业号

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 24, 2026

changedInput schema / properties / user_id / description

Previous value: -"小红书用户 user_id。请直接复制笔记搜索结果、商品评价、笔记详情、标签页笔记列表、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"New value: +"小红书用户 user_id。用户已提供时原样使用；否则可从笔记搜索、商品评价、商品评价回复、笔记详情、标签页笔记列表、用户信息或用户发帖列表结果中的 user_id/author.user_id 复制；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称。"

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties / points

Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "red_id",
-  "bio",
-  "verified",
-  "verification_category",
-  "is_professional_account",
-  "verification_name",
-  "is_enterprise_account",
-  "profile_tags",
-  "follower_count",
-  "following_count",
-  "posted_note_count",
-  "received_like_count",
-  "received_collect_count",
-  "ip_location"
-]New value: +[
+  "user_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "red_id",
+  "bio",
+  "verified",
+  "verification_category",
+  "is_professional_account",
+  "verification_name",
+  "is_enterprise_account",
+  "profile_tags",
+  "follower_count",
+  "following_count",
+  "posted_note_count",
+  "received_like_count",
+  "received_collect_count",
+  "ip_location",
+  "points"
+]

Changed1 schema field changedAug 14, 2026

changedInput schema / properties / user_id / description

Previous value: -"小红书用户 user_id。请直接复制笔记搜索结果、笔记详情、标签页笔记列表、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"New value: +"小红书用户 user_id。请直接复制笔记搜索结果、商品评价、笔记详情、标签页笔记列表、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"

Changed1 schema field changedAug 13, 2026

changedInput schema / properties / user_id / description

Previous value: -"小红书用户 user_id。请直接复制搜索结果、笔记详情、标签页笔记列表、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"New value: +"小红书用户 user_id。请直接复制笔记搜索结果、笔记详情、标签页笔记列表、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"

Changed1 schema field changedAug 12, 2026

changedInput schema / properties / user_id / description

Previous value: -"小红书用户 user_id。请直接复制搜索结果、笔记详情、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"New value: +"小红书用户 user_id。请直接复制搜索结果、笔记详情、标签页笔记列表、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"

Changed6 schema fields changedJun 26, 2026

addedOutput schema / properties / is_enterprise_account

Added value: +{
+  "description": "是否为企业账号",
+  "type": "boolean"
+}

addedOutput schema / properties / is_professional_account

Added value: +{
+  "description": "是否为专业号",
+  "type": "boolean"
+}

addedOutput schema / properties / profile_tags

Added value: +{
+  "description": "主页头部标签名称列表；没有标签时为空数组",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / verification_category / description

Previous value: -"认证类目/行业类目；未认证或没有认证类目时为空字符串"New value: +"认证补充信息；可能是行业类目或认证主体名称；未认证或没有认证信息时为空字符串"

addedOutput schema / properties / verification_name

Added value: +{
+  "description": "认证主体名称；没有认证主体时为空字符串",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "red_id",
-  "bio",
-  "verified",
-  "verification_category",
-  "follower_count",
-  "following_count",
-  "posted_note_count",
-  "received_like_count",
-  "received_collect_count",
-  "ip_location"
-]New value: +[
+  "user_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "red_id",
+  "bio",
+  "verified",
+  "verification_category",
+  "is_professional_account",
+  "verification_name",
+  "is_enterprise_account",
+  "profile_tags",
+  "follower_count",
+  "following_count",
+  "posted_note_count",
+  "received_like_count",
+  "received_collect_count",
+  "ip_location"
+]

Changed1 schema field changedMay 29, 2026

changedInput schema / properties / user_id / description

Previous value: -"小红书用户 user_id。可直接传搜索、笔记详情或用户信息结果中的 user_id/author.user_id；只有主页链接时请使用 profile_url 入口"New value: +"小红书用户 user_id。请直接复制搜索结果、笔记详情、用户信息或用户发帖列表返回的 user_id/author.user_id；如果只有主页链接，请使用 profile_url 入口；不要传小红书号、昵称或主页名称"

Changed1 schema field changedMay 28, 2026

changedInput schema / properties / user_id / description

Previous value: -"小红书用户 user_id。可直接传其他结果中的 author.user_id 或用户信息工具返回的 user_id"New value: +"小红书用户 user_id。可直接传搜索、笔记详情或用户信息结果中的 user_id/author.user_id；只有主页链接时请使用 profile_url 入口"

Changed2 schema fields changedMay 18, 2026

addedOutput schema / properties / ip_location

Added value: +{
+  "description": "用户 IP 属地；没有 IP 属地时为空字符串",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "user_id",
-  "name",
-  "avatar_url",
-  "profile_url",
-  "red_id",
-  "bio",
-  "verified",
-  "verification_category",
-  "follower_count",
-  "following_count",
-  "posted_note_count",
-  "received_like_count",
-  "received_collect_count"
-]New value: +[
+  "user_id",
+  "name",
+  "avatar_url",
+  "profile_url",
+  "red_id",
+  "bio",
+  "verified",
+  "verification_category",
+  "follower_count",
+  "following_count",
+  "posted_note_count",
+  "received_like_count",
+  "received_collect_count",
+  "ip_location"
+]

Changed5 schema fields changedMay 8, 2026

changedOutput schema / properties / avatar_url / description

Previous value: -"用户头像链接；当前不可用时为 null"New value: +"用户头像链接；没有头像链接时为 null"

changedOutput schema / properties / bio / description

Previous value: -"用户个人简介（biography）；当前不可用时为空字符串"New value: +"用户个人简介（biography）；没有简介时为空字符串"

changedOutput schema / properties / profile_url / description

Previous value: -"用户主页链接；当前不可用时为 null"New value: +"用户主页链接；没有主页链接时为 null"

changedOutput schema / properties / red_id / description

Previous value: -"用户公开小红书号；当前不可用时为空字符串"New value: +"用户公开小红书号；没有小红书号时为空字符串"

changedOutput schema / properties / verification_category / description

Previous value: -"认证类目/行业类目；当前不可用时为空字符串"New value: +"认证类目/行业类目；未认证或没有认证类目时为空字符串"

AddedApr 27, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation in an open world. The description itself adds no further behavioral context (e.g., error handling, rate limits), but this is acceptable given the annotations cover the safety profile. No contradiction exists.

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?

The description is a single, concise sentence that immediately conveys the tool's purpose. There is no extraneous information, and all additional guidance is appropriately placed in the schema, keeping the description lean and front-loaded.

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?

The tool has a single parameter fully documented in the schema, annotations declare safety traits, and an output schema exists so return values are separately specified. The description is complete for a simple, read-only lookup tool—nothing an agent needs to call it correctly 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 description coverage is 100%, and the user_id parameter is thoroughly documented with a description explaining origin, alternatives, and exclusions. The tool description adds no additional parameter semantics, but the schema already carries the full burden, 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?

The description '根据 user_id 获取单个小红书用户信息' clearly states the action (get) and resource (single Xiaohongshu user info) and specifies the input method (by user_id). It distinguishes itself from the sibling tool xhs_get_user_info_by_profile_url via the parameter schema's note about using profile_url for home page links, so an agent can tell them apart.

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?

The parameter description explicitly provides usage guidance: it instructs to use user_id as-is when provided, where to copy it from other results, and specifically says '如果只有主页链接，请使用 profile_url 入口' (if only home page link, use profile_url), while also warning against using Xiaohongshu number, nickname, or homepage name. This clearly routes the agent to the correct tool and input.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?