SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_pgy_get_note_detail_by_note_url

Read-only

根据笔记链接、短链接或分享文案获取小红书蒲公英单篇笔记商业增强详情。仅适用于已入驻蒲公英博主的笔记；用户明确要求蒲公英商业数据时使用，普通笔记详情使用普通详情工具。用户只提曝光量、阅读量或报价且上下文未明确蒲公英口径时，先澄清商业口径和成功 20 积分的费用；上下文已明确时不重复确认。这是蒲公英商业口径数据，不等同普通公开笔记详情；成功调用扣减 20 积分，失败不扣费。查询明确无商业数据时按博主未入驻蒲公英处理，返回 pgy_commercial_data_unavailable，不换 ID/链接入口重试；超时、鉴权和余额不足等错误不表示未入驻。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`note_url`	Yes	小红书笔记链接、短链接或分享文案。支持小红书笔记长链接、xhslink.com / xhslink.cn / xhsurl.com / xhsurl.cn 短链接，以及包含上述链接的完整分享文案。

Output Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	蒲公英笔记标题
`video`	Yes	视频摘要信息；视频笔记返回对象，图文笔记为 null
`author`	Yes	作者信息；详情页不返回小红书号
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。
`content`	Yes	笔记正文
`note_id`	Yes	note_id 是小红书笔记 ID。已有完整 note_id 时原样使用；否则可从笔记搜索、笔记详情、评论、标签页笔记列表或用户发帖列表结果复制；不得截断、缩写、脱敏、补全、格式化、重组，也不得只传前缀。
`note_url`	Yes	note_url 是可打开笔记内容所需的完整 URL。任何使用该返回链接的场景都必须原样保留完整 URL，包括 xsec_token 等 query 参数；例如最终回答、展示、引用、存储、输出或传递；不得修改、截断、脱敏、规范化、重组，也不得用 note_id 重新拼接链接。
`note_type`	Yes	笔记类型；当前公开值固定为 image 或 video
`like_count`	Yes	点赞数
`read_count`	Yes	笔记阅读量
`image_items`	Yes	图片结构化明细；每项都表示一张图片
`share_count`	Yes	分享数
`update_time`	Yes	更新时间，秒级 Unix 时间戳
`video_price`	Yes	视频笔记报价
`publish_time`	Yes	发布时间，秒级 Unix 时间戳
`collect_count`	Yes	收藏数
`comment_count`	Yes	评论数
`picture_price`	Yes	图文笔记报价
`exposure_count`	Yes	笔记曝光量
`cover_image_url`	Yes	统一封面图

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 26, 2026

addedOutput schema / properties / image_items / items / properties / height

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "图片高度，像素；没有时为 null"
+}

addedOutput schema / properties / image_items / items / properties / width

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "图片宽度，像素；没有时为 null"
+}

changedOutput schema / properties / image_items / items / required

Previous value: -[
-  "image_url",
-  "live_photo"
-]New value: +[
+  "image_url",
+  "width",
+  "height",
+  "live_photo"
+]

changedOutput schema / properties / video / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "duration_ms": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "视频时长，单位毫秒；没有时长时为 null"
-      },
-      "video_url": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "视频链接；没有视频链接时为 null"
-      }
-    },
-    "required": [
-      "video_url",
-      "duration_ms"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "duration_ms": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频时长，单位毫秒；没有时长时为 null"
+      },
+      "height": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频高度，像素；没有时为 null"
+      },
+      "video_url": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频链接；没有视频链接时为 null"
+      },
+      "width": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "description": "视频宽度，像素；没有时为 null"
+      }
+    },
+    "required": [
+      "video_url",
+      "duration_ms",
+      "width",
+      "height"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed1 schema field changedAug 24, 2026

changedOutput schema / properties / note_id / description

Previous value: -"note_id 是小红书笔记 ID。必须原样复制笔记搜索、笔记详情、评论、标签页笔记列表或用户发帖列表返回的完整 note_id；不得截断、缩写、脱敏、补全、格式化、重组，也不得只传前缀。"New value: +"note_id 是小红书笔记 ID。已有完整 note_id 时原样使用；否则可从笔记搜索、笔记详情、评论、标签页笔记列表或用户发帖列表结果复制；不得截断、缩写、脱敏、补全、格式化、重组，也不得只传前缀。"

AddedAug 20, 2026

TDQS

A4.1/5.0

Behavior1/5

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

The description transparently discloses cost, failure charging, special return values, and retry guidance, but it directly contradicts the annotation readOnlyHint=true by stating that a successful call deducts 20 points. Deducting points is a state-modifying side effect, so the description conflicts with the read-only annotation.

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 well-structured and dense with useful operational information, covering functionality, applicability, cost, error semantics, and retry policy. It is slightly repetitive in emphasizing the distinction from ordinary public note details, but overall every sentence contributes value.

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 description provides complete operational context: what data is returned, when to use the tool, cost and failure conditions, the meaning of pgy_commercial_data_unavailable, and how to handle timeout, auth, and balance errors. An agent has enough information to invoke it correctly and handle edge cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter note_url is fully described, including supported long links, short link domains (xhslink.com, xhsurl.com, etc.), and full share text containing such links. This adds practical parsing details beyond the schema and leaves no ambiguity about acceptable input formats.

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 states the tool fetches Pugongying commercial enhanced note details from note links, short links, or share text. It explicitly distinguishes this tool from ordinary note detail retrieval and from the by-note-id variant, so an agent can select it correctly.

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 description gives explicit when-to-use guidance: use only for Pugongying commercial data when the user explicitly requests it, and use the ordinary detail tool for normal notes. It also instructs the agent to clarify the commercial caliber and the 20-point cost when context is ambiguous, and not to reconfirm when context is already clear.

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?