SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_note_share_link_by_note_url

Read-only

根据小红书笔记链接、短链接或分享文案获取完整分享内容和分享短链接。已有 note_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": {
      "note_url": "<note_url>"
    },
    "name": "xhs_get_note_share_link_by_note_url"
  }
}

Input Schema

Name	Required	Description	Default
`note_url`	Yes	小红书笔记页面链接、短链接或包含链接的分享文案。

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/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that it accepts not only a page URL but also a short link or a share text containing the link, implying input extraction behavior, which is useful. Beyond that it does not describe pagination, failure modes, or whether the returned short link is newly generated, so it adds only moderate value.

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?

It consists of two sentences: the first states the capability and the second states the disambiguation rule, with the primary action front-loaded and no filler.

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?

An output schema exists, so return values do not need to be described, and both annotations are set, so the tool is low-complexity and well covered. The only minor gap is the unresolved relationship with xhs_get_share_info, which an agent could confuse with this tool.

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_url parameter, so the schema already explains the accepted formats. The description restates the same three input forms rather than adding format examples or normalization rules beyond what the schema provides, so it meets the baseline rather than exceeding it.

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 names a specific verb and resource combination: it takes a note URL, short link, or share text and returns the complete share content plus the short share link. It also explicitly names the by-ID sibling as the alternative, so an agent can tell this tool apart from xhs_get_note_share_link_by_note_id 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear routing rule: when a note_id already exists, use the by-ID tool; otherwise this URL-based tool is the correct choice. It does not discuss the overlap with the similarly named xhs_get_share_info sibling, which leaves a small ambiguity, but the primary when-to-use guidance is explicit.

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?