SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_user_id_by_encrypted_user_id

Read-only

根据完整加密用户 ID 获取稳定 user_id。仅需单独转换 ID 时使用；查询用户信息或作品可直接使用已有用户 ID 或主页链接，无需先调用本工具。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "encrypted_user_id": "<encrypted_user_id>"
    },
    "name": "xhs_get_user_id_by_encrypted_user_id"
  }
}

Input Schema

Name	Required	Description	Default
`encrypted_user_id`	Yes	小红书加密用户 ID。用户已提供时直接原样使用；请传入完整 29 位小写十六进制值；不要传 24 位 user_id、小红书号、昵称或主页链接

Output Schema

Name	Required	Description	Default
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`user_id`	Yes	稳定用户 user_id

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

changedOutput schema / properties / points / description

Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"

changedOutput schema / properties / points / properties / balance / description

Previous value: -"本次接口完成时看到的当前积分余额，可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时，回退到本次预扣后的余额快照。余额可为负数。"

Changed2 schema fields changedNov 4, 2026
- changedOutput schema / properties / points / properties / balance / description
```
Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额，可为负数。"
```
- removedOutput schema / properties / points / properties / balance / minimum
```
Removed value: -0
```
Changed2 schema fields changedNov 3, 2026
- addedOutput schema / properties / user_id / title
```
Added value: +"User Id"
```
- addedOutput schema / title
```
Added value: +"UserIdDecryptData"
```
AddedSep 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value by warning that this is a redundant precondition for most workflows, preventing an unnecessary call. It does not discuss failure behavior for malformed IDs, which the schema handles instead.

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?

Two short sentences: the first defines the operation, the second front-loads the usage restriction and the alternative. Nothing is redundant or padded.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the single parameter is fully documented in the schema. The description covers purpose and usage routing adequately; only edge-case handling (invalid or truncated IDs) is left implicit.

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 parameter's description already specifies a full 29-character lowercase hex value and rules out 24-character user_ids, nicknames, and profile links. The description only restates 'complete encrypted user ID', adding no 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?

The description states a precise verb+resource pair: convert a complete encrypted user ID into a stable user_id. It also delimits scope by noting that user-info and user-post queries do not need this conversion step, which separates it from siblings such as xhs_get_user_info_by_user_id and xhs_get_user_posted_notes_by_user_id.

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?

It gives explicit when-to-use ('only when you need to convert an ID on its own') and when-not-to-use ('querying user info or works can use an existing user ID or profile link directly, no need to call this tool first'), effectively routing the agent toward the profile-url and user-id siblings.

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?