xhs_searchMcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_xhs_hot_noteA | 打开小红书，按关键词搜索，筛选图文笔记并按最多点赞排序，返回第一篇普通笔记的标题、正文和图片。调用前须由部署方准备有效登录态。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no risk of confusing it with another, so the selection is unambiguous. The tool description clearly states its purpose and required conditions.
The tool name 'search_xhs_hot_note' uses a clear verb_noun structure, with 'search' as the action and 'xhs_hot_note' as the target. Since it is the only tool, naming consistency is naturally maintained.
Having exactly one tool for a search service is too few, as it does not provide any redundancy or alternative variations for the user's search needs. The rubric specifically notes that one tool for the apparent scope is a score of 2.
The tool offers a very narrow capability—returning a single hot note for a keyword search—leaving no support for multiple results, different content types, or additional search parameters. This significant lack of coverage means agents will encounter dead ends when requiring fuller search functionality.