xhs-mcp

xhs_explore

Retrieve the current trending feed from Xiaohongshu to spot popular content and understand what resonates with Chinese consumers. Supports category-specific feeds for tailored exploration.

Instructions

Get the current trending/explore feed from Xiaohongshu homepage. Shows what content is currently popular on the platform. Great for trend spotting and understanding what resonates with Chinese consumers.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xhs_explore"
  }
}

Input Schema

Name	Required	Description	Default
`category`	No	Feed category (leave empty for recommended). Examples: homefeed_recommend, homefeed.fashion_v3, homefeed.food_v3

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 8, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does communicate that the tool returns a real-time, platform-level feed, which is useful. But it does not mention any behavioral details such as authentication requirements, rate limits, pagination, or output format. For a read-only feed tool, this is acceptable but not exemplary.

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 concise: two sentences that lead with the action, then describe the benefit. Every sentence earns its place, with no redundancy or filler.

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's simplicity (single optional parameter, no output schema), the description covers the essential purpose and usage context. It could be improved by mentioning the return format or pagination behavior, but it is largely complete for a trending-feed retrieval tool.

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?

The schema fully describes the single parameter 'category' with examples, giving 100% coverage. The description does not add extra meaning about the parameter's effect beyond the schema, so the baseline of 3 applies.

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 fetches the current trending/explore feed from the Xiaohongshu homepage, using a specific verb ('Get') and resource ('trending/explore feed'). It distinguishes itself from sibling tools like search, note detail, and user profiles by focusing on platform-wide trends rather than specific user or search-driven content.

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 provides clear context for when to use the tool: 'Great for trend spotting and understanding what resonates with Chinese consumers.' This implies usage for high-level market/trend analysis. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a full 5.

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

Deploy Server