Skip to main content
Glama
DevinChen2014

SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_note_detail_by_note_id

Read-only

Retrieve detailed information about a Xiaohongshu note using its unique note ID. Returns complete note data including URL and metadata.

Instructions

根据 note_id 获取单篇小红书笔记详情。 返回的 note_url 非 null 时,在任何使用场景都必须原样保留完整 URL,包括 xsec_token 等 query 参数;例如最终回答、展示、引用、存储、输出或传递;不得用 note_id 重新拼接链接;note_url 为 null 时不要用 note_id 合成公开链接。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
note_idYesnote_id 是 24 位小写十六进制稳定笔记 ID。必须原样复制搜索、详情、评论或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes笔记标题
videoYes视频摘要信息;无可用视频摘要时为 null
authorYes作者信息;详情页不返回小红书号
contentYes笔记正文
note_idYesnote_id 是 24 位小写十六进制稳定笔记 ID。必须原样复制搜索、详情、评论或用户发帖列表返回的完整 note_id;不得截断、缩写、脱敏、补全、格式化、重组,也不得只传前缀。
note_urlYesnote_url 是可打开笔记内容所需的完整 URL。任何使用该返回链接的场景都必须原样保留完整 URL,包括 xsec_token 等 query 参数;例如最终回答、展示、引用、存储、输出或传递;不得修改、截断、脱敏、规范化、重组,也不得用 note_id 重新拼接链接。无法提供可用链接时为 null;note_url 为 null 时不要用 note_id 合成公开链接。
note_typeYes笔记类型;当前公开值固定为 image 或 video
like_countYes点赞数
topic_tagsYes笔记详情中的话题标签;无话题时为空数组
image_itemsYes图片结构化明细;每项都表示一张图片,Live 图会在对应项携带 live_photo 摘要
ip_locationYes笔记发布时的 IP 属地;没有 IP 属地时为空字符串
share_countYes分享数
update_timeYes更新时间,秒级 Unix 时间戳;没有有效更新时间时为 null
publish_timeYes发布时间,秒级 Unix 时间戳
collect_countYes收藏数
comment_countYes评论数
cover_image_urlYes统一封面图
mentioned_usersYes笔记正文中 @ 到的用户列表;无 @ 时为空数组
Behavior4/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds actionable behavioral detail about note_url handling, which is beyond what annotations provide.

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 focused sentences: one for purpose, one for critical usage rule. No redundancy or unnecessary information.

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 simple one-parameter tool with output schema present, the description is complete. It covers purpose, input constraint, post-usage rule, and is sufficient for correct invocation.

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 already fully covers the note_id parameter (100% coverage). The tool description does not add new semantic meaning about the parameter beyond what the schema provides.

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's purpose: fetching single note details by note_id. It distinguishes from sibling tools like xhs_get_note_detail_by_note_url by specifying the input identifier type.

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?

Provides explicit guidance on handling the returned note_url, including preservation and when not to synthesize. While it doesn't explicitly compare with all siblings, the context implies appropriate use cases based on note_id vs URL.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DevinChen2014/xiaohongshu-xhs-rednote-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server