Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

xiaohongshu_note_comments

Fetch a public Xiaohongshu note's comments anonymously using the note URL or note_id with xsec_token, including replies and pagination cursors. Use the returned cursor to fetch the next page.

Instructions

Anonymous Xiaohongshu note comments. Returns one page of a public note's comments using a browser-minted signed request, with no account or login. Pass the note_url returned by /xiaohongshu/explore (it carries the required xsec_token). Each item includes the comment id, text, like/sub-comment counters, creation time, IP location when the site exposes it, a public author card, and up to five replies. has_more and cursor continue pagination: pass the returned cursor to fetch the next page. Comments are read from the anonymous signed API, so a stale note token returns an upstream error; re-run /xiaohongshu/explore for a fresh note_url. Search results and profiles are not exposed because they require login.

Input Schema

NameRequiredDescriptionDefault
urlNoNote URL carrying xsec_token, normally the note_url returned by /xiaohongshu/explore. Pass url, or both note_id and xsec_token.
cursorNoPagination cursor from a previous response
note_idNo24-character hex note id from an explore card (requires xsec_token)
xsec_tokenNoShort-lived feed-issued token that accompanies note_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: anonymous browser-minted signed request, no account/login needed, page-scoped returns, stale-token behavior returning an upstream error, and remediation (re-run explore). This is exactly the operational context an agent needs before calling.

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?

Front-loaded with purpose, then prerequisites, return shape, pagination, and failure handling in a logical flow. Dense but every sentence contributes distinct information with no filler.

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?

No output schema exists, yet the description enumerates the returned fields (comment id, text, counters, creation time, IP location, author card, up to five replies) and documents pagination signals (has_more, cursor). Nothing an agent needs to call and interpret results is missing.

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 coverage is 100%, so baseline is 3; the description adds value by tying url to the explore-returned note_url that carries xsec_token and by clarifying the cursor continuation loop. It largely restates what the schema already documents, so it doesn't fully exceed the baseline.

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?

States a specific verb and resource ('Returns one page of a public note's comments') with clear scope (anonymous, one page). It is trivially distinguishable from siblings like xiaohongshu_explore and xiaohongshu_note, and even names explore as the source of the URL.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to pass the note_url from /xiaohongshu/explore, explains pagination via cursor, and states what is NOT available ('Search results and profiles are not exposed because they require login'). Covers when-to-use, how to continue, and exclusions.

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

Deploy Server

Other Tools