Skip to main content
Glama
DevinChen2014

SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_topic_notes_by_topic_url

Read-only

Fetch notes from a Xiaohongshu topic page using a URL, short link, or share text. Sort by hot or time, and paginate with page_token.

Instructions

根据话题页链接、短链接或分享文案获取标签页笔记列表,支持 sort_type 排序和 page_token 翻页。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sort_typeNo标签页笔记排序方式,可选:hot(最热,默认)、time_descending(最新)hot
topic_urlYes小红书话题页链接、短链接或分享文案。支持以下形式:1) xiaohongshu.com/topic/normal/... 话题页长链;2) xhslink.com / xhslink.cn / xhsurl.com / xhsurl.cn 短链接;3) 包含上述任一链接的完整分享文案。
page_tokenNo分页令牌。首次请求留空;继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回。page_token 是不透明分页令牌,只绑定当前标签页和排序链路,不能跨 page_id 或排序复用;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes标签页笔记列表
pointsYes本次成功调用的积分消耗与调用完成时的账户积分余额。
next_page_tokenYes下一页不透明分页令牌;非空表示可尝试请求下一页,为空表示当前没有可继续的下一页令牌。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回。next_page_token 只绑定当前标签页和排序链路,不能跨 page_id 或排序复用;items 为空时不要单独据此判断结束;不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成,不得用省略号替换中间内容。
total_note_countYes标签页笔记总数
total_user_countYes标签页涉及用户总数

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.6

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds only that sorting and pagination are supported, which is already visible in the schema; it contributes little extra behavioral context beyond the 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?

A single sentence states the purpose and key capabilities with no filler. Every element in the description 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?

With a full input schema, output schema, and read-only annotations, the description is sufficient for an agent to select and invoke the tool correctly. It could add an explicit pointer to xhs_get_topic_notes_by_page_id for page-ID scenarios, but that is a routing nicety, not an invocation gap.

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%, so the schema already documents topic_url formats, sort_type enum, and page_token behavior. The description only restates that sorting and pagination are supported, adding no new meaning beyond the schema.

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 states a specific verb and resource: it fetches the topic notes list from a topic URL, short link, or share text. This also differentiates it from the sibling xhs_get_topic_notes_by_page_id, which uses a page ID instead of a URL.

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 makes the intended trigger explicit: use this tool when the caller has a topic page link, short link, or share text. It does not mention the page_id alternative or state exclusions, so it misses the full 'when not to use' guidance.

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