Skip to main content
Glama

SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_user_info_by_profile_url

Read-only

根据主页链接、短链接或分享文案获取单个小红书用户信息。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profile_urlYes小红书主页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/user/profile/... 主页长链;2) xhslink.com / xhslink.cn / xhsurl.com / xhsurl.cn 短链接;3) 包含上述任一链接的完整分享文案。请传主页链接,不要传笔记链接。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
bioYes用户个人简介(biography);没有简介时为空字符串
nameYes用户名称
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
red_idYes用户公开小红书号;没有小红书号时为空字符串
user_idYes用户 user_id
verifiedYes是否已认证
avatar_urlYes用户头像链接;没有头像链接时为 null
ip_locationYes用户 IP 属地;没有 IP 属地时为空字符串
profile_urlYes用户主页链接;没有主页链接时为 null
profile_tagsYes主页头部标签名称列表;没有标签时为空数组
follower_countYes粉丝数
following_countYes关注数
posted_note_countYes已发布笔记数
verification_nameYes认证主体名称;没有认证主体时为空字符串
received_like_countYes用户内容累计收到的点赞数
is_enterprise_accountYes是否为企业账号
verification_categoryYes认证补充信息;可能是行业类目或认证主体名称;未认证或没有认证信息时为空字符串
received_collect_countYes用户内容累计被收藏数
is_professional_accountYes是否为专业号

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / profile_url / description
      Previous value: -"小红书主页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/user/profile/... 主页长链;2) xhslink.com / xhslink.cn 短链接;3) 包含上述任一链接的完整分享文案。请传主页链接,不要传笔记链接。"New value: +"小红书主页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/user/profile/... 主页长链;2) xhslink.com / xhslink.cn / xhsurl.com / xhsurl.cn 短链接;3) 包含上述任一链接的完整分享文案。请传主页链接,不要传笔记链接。"
  3. Changed1 schema field changed
    • changedInput schema / properties / profile_url / description
      Previous value: -"小红书主页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/user/profile/... 主页长链;2) xhslink.com 短链接;3) 包含上述任一链接的完整分享文案。请传主页链接,不要传笔记链接。"New value: +"小红书主页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/user/profile/... 主页长链;2) xhslink.com / xhslink.cn 短链接;3) 包含上述任一链接的完整分享文案。请传主页链接,不要传笔记链接。"
  4. Changed6 schema fields changed
    • 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"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / profile_url / description
      Previous value: -"小红书主页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/user/profile/... 主页长链;2) xhslink.com 短链接;3) 包含上述任一链接的完整分享文案。解析后的最终链接必须是用户主页链接。"New value: +"小红书主页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/user/profile/... 主页长链;2) xhslink.com 短链接;3) 包含上述任一链接的完整分享文案。请传主页链接,不要传笔记链接。"
  6. Changed2 schema fields changed
    • 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"
      +]
  7. Changed5 schema fields changed
    • 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: +"认证类目/行业类目;未认证或没有认证类目时为空字符串"
  8. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true (safe read) and openWorldHint=true (results may vary). The description adds valuable behavioral context beyond annotations: it clarifies that the tool accepts multiple URL formats and share text, and explicitly prohibits note links. No contradictions with annotations.

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?

The description is a single sentence that directly states the tool's purpose and input options. It is concise and front-loaded, with no wasted words. Could slightly improve by adding a brief usage hint, but overall efficient.

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?

Given the tool's low complexity (one parameter, output schema present, annotations provided), the description is fully adequate. It specifies the allowed input formats and what to avoid, while the output schema covers return values. No gaps remain for an agent to use this tool 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?

The input schema covers 100% of parameters, with a detailed description of the 'profile_url' parameter. The tool description repeats the supported formats but adds no new semantic meaning beyond what the schema already provides. 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 clearly identifies the action ('get') and resource ('single Xiaohongshu user info'), and specifies the input type (profile link, short link, or share text). This distinguishes it from sibling tools like 'xhs_get_user_info_by_user_id' (which takes a user ID) and 'xhs_get_user_posted_notes_by_profile_url' (which retrieves notes, not user info).

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?

The description implicitly suggests usage when a profile URL is available, and the schema explicitly warns not to pass note links. However, it does not explicitly compare to alternatives or state when to use this tool versus 'xhs_get_user_info_by_user_id' or other siblings. The guidance is present but not explicit.

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