A
licenseB
qualityF
maintenanceEnables users to search and retrieve content from Xiaohongshu (Red Book) platform with smart search capabilities and rich data extraction including note content, author information, and images.
1
62 npm
29
MIT
GoAI Moat Xiaohongshu Products
by com.goaimoat
Server Details
Search Xiaohongshu products by keyword.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- jayniebingyu-cyber/goaimoat-mcp
- GitHub Stars
- 0
TDQS
A3.6/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no possibility of confusion between tools. The tool's purpose is clear and distinct.
Naming Consistency4/5
The single tool follows a clear verb_noun pattern ('search_xhs_products'), which is consistent and readable. With only one tool, there is no pattern conflict to assess.
Tool Count2/5
A single tool is far too few for a server ostensibly focused on Xiaohongshu products, leaving it feeling skeletal and underpowered for anything beyond simple searches.
Completeness2/5
The server only supports searching products; there are no operations for retrieving details, listing categories, or managing any product-related workflow. This is a significant gap for a product-focused server.
Available Tools
1 toolsearch_xhs_productsSearch Xhs ProductsAInspect
Search Xiaohongshu (RED) products by keyword.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| keyword | Yes | Product keyword. |
Output Schema
ParametersJSON Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
A3.7/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely restates the tool's name and provides no insight into result limits, pagination, authentication requirements, or read-only vs. mutating behavior. For a search tool this is a notable gap.
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 a single, front-loaded sentence that states the tool's function and scope with no redundancy or filler. It is efficiently sized for the tool's simplicity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has low complexity (one parameter, output schema present), and the description does establish purpose. However, it omits any behavioral or usage context beyond the bare statement, though the output schema mitigates the need to explain return values. Overall, it is minimally adequate but has clear gaps.
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%, with the keyword parameter already described as 'Product keyword.' The description adds no additional semantic meaning beyond that, so the baseline of 3 is appropriate.
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 uses a specific verb ('search') with a clearly identified resource ('Xiaohongshu (RED) products') and the search modality ('by keyword'). It is unambiguous and immediately understood, even without sibling tools for comparison.
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 clearly implies when to use this tool: when a keyword-based product search on Xiaohongshu is needed. Since no sibling tools are listed, there are no alternatives or exclusions to mention, so the context is clear without explicit when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
search_xhs_products
Related MCP Connectors
XHS hot search/suggestions、note/product search/details、PGY、comments/replies、users/posts、transcript
搜索笔记、浏览首页推荐、查看笔记内容与评论，并发表你的评论。直接在工作流中与小红书内容互动，高效跟进话题。
Search Korean cosmetics from Olive Young, Daiso, Naver, Coupang, 11st with EWG ingredient analysis.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI clients to search Xiaohongshu notes by brand and category, batch extract comments, and perform keyword/sentiment/heat analysis, with results exported as Excel and JSON reports.4MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search real content from Xiaohongshu and Zhihu, supporting keyword search, note details, and question retrieval.84MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to search Xiaohongshu notes, analyze favorites, and extract text from images for social media research.716 npm20MIT
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.