SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_note_share_link_by_note_id

Read-only

根据小红书笔记 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": {
      "note_id": "<note_id>"
    },
    "name": "xhs_get_note_share_link_by_note_id"
  }
}

Input Schema

Name	Required	Description	Default
`note_id`	Yes	小红书笔记 ID。

Output Schema

Name	Required	Description
`points`	Yes	本次成功调用的积分消耗与账户积分余额。
`short_url`	Yes	小红书笔记分享短链接。
`share_text`	Yes	包含分享短链接的完整分享内容，可复制分享。

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
```
Changed3 schema fields changedNov 3, 2026
- addedOutput schema / properties / share_text / title
```
Added value: +"Share Text"
```
- addedOutput schema / properties / short_url / title
```
Added value: +"Short Url"
```
- addedOutput schema / title
```
Added value: +"NoteShareLinkData"
```
AddedOct 23, 2026

TDQS

A4.2/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 safety and openness profile is covered. The description adds that the output contains both full share content and a short link, but says nothing about rate limits, auth, or failure modes, so it is adequate rather than rich.

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 with zero filler: the primary action comes first and the sibling-routing note second. Every clause earns its place.

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?

Output schema exists, so return values need not be spelled out, and the single required parameter is fully documented in the schema. The only minor gap is that '完整分享内容' is not characterized at all, but an agent has everything needed to invoke the 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?

Schema description coverage is 100% for the single note_id parameter, and the description merely restates that the input is a Xiaohongshu note ID. With the schema doing the heavy lifting, the baseline of 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?

Uses a specific verb and resource ('获取完整分享内容和分享短链接' via note ID) and implicitly defines itself against the sibling xhs_get_note_share_link_by_note_url, so an agent can distinguish the two without opening either schema.

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 tool when you have a note ID, and switch to the by-URL share-link tool when you already hold a note link. That is a concrete when-to-use-alternative rule rather than an implied one.

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?