SocialDataX 小红书 Xiaohongshu XHS RedNote MCP

xhs_get_search_hot_list

Read-only

获取小红书搜索热榜。

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes	搜索热榜条目列表
`points`	Yes	本次成功调用的积分消耗与调用完成时的账户积分余额。

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 17, 2026

addedOutput schema / properties / points

Added value: +{
+  "additionalProperties": false,
+  "description": "本次成功调用的积分消耗与调用完成时的账户积分余额。",
+  "properties": {
+    "balance": {
+      "description": "本次接口完成时看到的当前积分余额。",
+      "minimum": 0,
+      "type": "integer"
+    },
+    "cost": {
+      "description": "本次请求最终确认消耗的积分。",
+      "minimum": 0,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "cost",
+    "balance"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "items"
-]New value: +[
+  "items",
+  "points"
+]

AddedMay 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description does not contradict these, but it adds no additional behavioral context—e.g., whether the list updates frequently, whether it requires authentication, or what happens if the list is unavailable. With annotations covering the key traits (read-only, open world), the lack of further detail is acceptable but not enhanced.

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 a single sentence in Chinese. It conveys the purpose efficiently without any filler. However, it could be slightly less terse if it included the English equivalent for non-Chinese agents.

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?

Given the tool has no parameters and has an output schema, the description is sufficient for understanding the tool's purpose. The output schema presumably defines the structure of the hot list, so the description does not need to explain return values. One might wish for additional context about what 'hot list' means (e.g., trending topics, searches), but the purpose is clear enough.

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

Parameters4/5

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

The input schema has zero parameters, so the description cannot add parameter details. With no parameters, the baseline is 4—the description is sufficient as there are no parameter semantics to elaborate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets the 小红书 search hot list (search hot list for Xiaohongshu). The verb '获取' (get) and resource '搜索热榜' (search hot list) are specific. Among sibling tools that focus on notes, comments, user info, products, and search results, this one uniquely addresses the hot list, providing good differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description implies this should be used when an agent or user wants the current trending/search hot list from Xiaohongshu. However, it does not explicitly state when to use this versus alternatives (e.g., when to prefer this over search functions like xhs_search_notes). No exclusions or context about frequency or user need are given.

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?