cn-scraper-mcp

Overview Schema Source Related Servers Discussions Admin

xiaohongshu_note

Retrieve Xiaohongshu note details including title, content, likes, tags, and comments using note_id and xsec_token from a search result. Provides structured note data for AI agents.

Instructions

获取小红书笔记详情（标题、正文、点赞、标签、评论）。

note_id 和 xsec_token 都来自同一条 xiaohongshu_search 结果。

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": {
      "note_id": "<note_id>",
      "xsec_token": "<xsec_token>"
    },
    "name": "xiaohongshu_note"
  }
}

Input Schema

Name	Required	Description	Default
`note_id`	Yes	笔记 ID（从 xiaohongshu_search 结果中的 noteId 字段）
`xsec_token`	Yes	反爬 token（从同一条 xiaohongshu_search 结果中的 xsec_token 字段）

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 17, 2026

TDQS

A4.3/5.0

Behavior3/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. It discloses what the tool returns but does not cover authentication needs, rate limits, or side effects. For a read-only fetch tool, this is adequate but not exceptional.

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 with no wasted words. The first sentence states purpose and contents, the second gives parameter source. Well-structured and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists and the description lists the key fields returned, the tool is fully specified. Parameter sources are clear, and the tool fits well within the sibling context.

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?

Schema descriptions already explain both parameters. The additional note that they come from the same search result adds value beyond the schema, reinforcing the dependency.

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 gets Xiaohongshu note details and lists specific fields (title, body, likes, tags, comments). It distinguishes from siblings like xiaohongshu_comments and xiaohongshu_search.

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 that note_id and xsec_token come from the same xiaohongshu_search result, providing clear usage context. It does not mention when not to use this tool, but the context is strong.

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