How do I organize feedback themes from RedNote comments?
How do I organize feedback themes from RedNote comments? Follow concrete contracts, examples and reviewable steps using Xiaohongshu (RedNote).
Copy the agent prompt manually
Answer
Start by inspecting the contracts and local samples for Xiaohongshu note comments, Xiaohongshu comment replies. Establish the input for xiaohongshu.notes.comments.list, then check whether its comment object contains the fields your task needs.
Produce a structured local result before mapping fields to table columns or document sections. Deduplicate by platform and content ID and retain source and observation time. Downloading a file and writing to another application are separate actions; this exercise sends nothing externally.
Relevant contracts
| Capability | Object | Shape | Pagination |
|---|---|---|---|
| xiaohongshu.notes.comments.list | Comment | items | Explicit cursor |
| xiaohongshu.comments.replies.list | Comment | items | Explicit cursor |
Input contract
Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.
- GET: supply exactly one of id / url.
| Method | Field | Type | Requirement | Meaning | Enum or bound | Example |
|---|---|---|---|---|---|---|
| GET | id | string | Optional / conditional | Note ID, 24 hexadecimal characters. With only a link or a share text, give it as url | — | "6a9c5884000000002b002d95" |
| GET | url | string | Optional / conditional | Link to the note, pasted as it is: the https://www.xiaohongshu.com/explore/… address from the browser, the https://www.xiaohongshu.com/discovery/item/… link the website shares (query parameters such as xsec_token are fine), a whole share text with such a link in it, or the xhslink.com short link the app copies (alone or in its share text). A short link is opened once to see which note it leads to; where it cannot be, paste the note's full link or its ID | — | — |
| GET | sort | string | Optional / conditional | Newest first (the default), or hottest first (most liked first) | ["latest","popular"] | — |
| GET | cursor | string | Optional / conditional | The `next_cursor` of the previous page. A new page is a new call. | — | — |
| GET | view | string | Optional / conditional | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |
| GET | fields | array | Optional / conditional | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |
Complete one verification
Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.
{
"capability": "xiaohongshu.notes.comments.list",
"method": "GET",
"params": {
"id": "6a9c5884000000002b002d95"
}
}Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗