xhs-mcp

xhs_user_profile

Retrieve Xiaohongshu user profiles with follower count, total likes, note count, and bio. Supports influencer research and competitive analysis.

Instructions

Get a Xiaohongshu user's profile including follower count, total likes, number of notes, and bio. Useful for influencer research and competitive analysis.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "xhs_user_profile"
  }
}

Input Schema

Name	Required	Description	Default
`user_id`	Yes	Xiaohongshu user ID (from note details or search results)

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 provided, the description carries the behavioral disclosure burden. It makes the read-only nature apparent through 'Get' and lists returned fields, but does not mention authorization requirements, rate limits, or data freshness. For a simple profile lookup this is acceptable, though not exhaustive.

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?

Two concise sentences: the first states the core purpose and return fields, the second provides practical use cases. There is no filler or redundancy, and important information is front-loaded.

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 only one required parameter and no output schema, the description compensates well by naming key profile fields and a use case. It does not cover error cases or edge conditions, but for a straightforward profile retrieval it is sufficiently complete.

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 single parameter user_id is fully described in the schema, including its source ('from note details or search results'), so schema coverage is 100%. The description adds no further parameter-specific detail, which is unnecessary given the schema already handles it.

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 identifies the resource (Xiaohongshu user profile) and specific data points (follower count, total likes, number of notes, bio). It naturally distinguishes from siblings like xhs_note_detail and xhs_user_notes by focusing on the profile-level resource.

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 explicitly states usefulness for influencer research and competitive analysis, providing clear context for when to use this tool. It does not explicitly rule out alternatives or provide when-not-to-use guidance, but the use cases are informative enough.

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

Deploy Server