SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_pgy_get_note_detail_by_note_id

Read-only

根据 note_id 获取小红书蒲公英单篇笔记商业增强详情，包括正文、图片或视频摘要、作者、曝光量、阅读量、点赞、收藏、评论、分享和创作者图文/视频合作报价（单位：人民币元；不是当前笔记的成交金额；零值不表示免费合作）。仅适用于已入驻蒲公英博主的笔记；用户明确要求蒲公英商业数据时使用，普通笔记详情使用普通详情工具。用户只提曝光量、阅读量或报价且上下文未明确蒲公英口径时，先澄清商业口径和成功 20 积分的费用；上下文已明确时不重复确认。这是蒲公英商业口径数据，不等同普通公开笔记详情；成功调用扣减 20 积分，失败不扣费。查询明确无商业数据时按博主未入驻蒲公英处理，返回 pgy_commercial_data_unavailable，不换 ID/链接入口重试；超时、鉴权和余额不足等错误不表示未入驻。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`note_id`	Yes	note_id 是小红书笔记 ID。已有完整 note_id 时原样使用；否则可从笔记搜索、笔记详情、评论、标签页笔记列表或用户发帖列表结果复制；不得截断、缩写、脱敏、补全、格式化、重组，也不得只传前缀。

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	静态图片明细；不包含 Live 图视频摘要，需要 Live 视频时使用普通笔记详情接口
`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.

Changed3 schema fields changedSep 25, 2026

changedOutput schema / properties / image_items / description

Previous value: -"图片结构化明细；每项都表示一张图片"New value: +"静态图片明细；不包含 Live 图视频摘要，需要 Live 视频时使用普通笔记详情接口"

removedOutput schema / properties / image_items / items / properties / live_photo

Removed value: -{
-  "description": "蒲公英当前未返回样本证实的 Live 图视频摘要，固定为 null",
-  "type": "null"
-}

changedOutput schema / properties / image_items / items / required

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

Changed2 schema fields changedSep 24, 2026

changedOutput schema / properties / picture_price / description

Previous value: -"图文笔记报价，单位：人民币元"New value: +"创作者图文笔记合作报价，单位：人民币元；不是当前笔记的成交金额；零值不表示免费合作"

changedOutput schema / properties / video_price / description

Previous value: -"视频笔记报价，单位：人民币元"New value: +"创作者视频笔记合作报价，单位：人民币元；不是当前笔记的成交金额；零值不表示免费合作"

Changed2 schema fields changedSep 24, 2026

changedOutput schema / properties / picture_price / description

Previous value: -"图文笔记报价"New value: +"图文笔记报价，单位：人民币元"

changedOutput schema / properties / video_price / description

Previous value: -"视频笔记报价"New value: +"视频笔记报价，单位：人民币元"

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"
+  }
+]

Changed2 schema fields changedAug 24, 2026

changedInput schema / properties / note_id / description

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

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

Behavior5/5

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

Annotations already mark readOnlyHint=true, and the description adds substantial behavioral context: successful calls deduct 20 积分, failed calls do not, the data is commercial and differs from public note details, zero quotation values do not mean free collaboration, and timeout/auth/insufficient-balance errors do not imply the creator is not入驻蒲公英. No contradiction 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and payload, then moves to usage boundaries, cost, and error handling. Every sentence carries operational value; there is no filler, even though the text is longer than average.

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?

For a tool with one parameter, an output schema, and annotations, the description covers all agent-relevant context: when to use, what it returns, cost, failure semantics, unavailable-data handling, and how it differs from ordinary note details. Nothing critical is missing.

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%: the single note_id parameter already has a rich description covering how to obtain it and forbidding truncation/formatting. The description only repeats “根据 note_id,” so it adds little beyond the schema, which matches the baseline for high schema coverage.

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 opens with a specific verb and resource: “根据 note_id 获取小红书蒲公英单篇笔记商业增强详情” and enumerates the exact fields returned (正文、图片/视频摘要、作者、曝光量、阅读量、点赞、收藏、评论、分享、报价). It also explicitly contrasts itself with the ordinary detail tool, so an agent can distinguish it from sibling xhs_get_note_detail_by_note_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?

Usage is explicit: use only for 蒲公英入驻博主 notes, and use when the user explicitly requests 蒲公英 commercial data; ordinary note details should use the ordinary detail tool. It also gives a concrete clarification rule when the user mentions 曝光量/阅读量/报价 without an explicit 蒲公英 context, and warns against retrying when pgy_commercial_data_unavailable is returned.

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?