Xiaohongshu Note Comments
Collect public comments, engagement details, author information, and timestamps from one Xiaohongshu note
原文 · en-US訳文に戻す
概要
Public comments on a Xiaohongshu note reveal how readers respond in their own words, which details attract attention, and where follow-up discussion develops. This Data App turns the public comment area of one note into a consistent dataset containing comment text, author details, reply relationships, engagement snapshots, media references, visible location text, and timestamps.
The result is designed for repeatable analysis instead of manual scrolling. It preserves the original wording and connects each comment to its note and discussion thread, making reactions easier to compare across collection runs and helping teams inspect both top-level comments and replies with the same set of fields.
Data notes
The data covers comments and author details that are publicly visible for the supplied Xiaohongshu note at collection time. Each normal record is identified by its Comment ID, which removes duplicates across collected pages. Private, deleted, restricted, and login-only comments are outside the coverage.
Like count, Reply count, View count, account details, and visible location values are snapshots and may change after collection. Count values and classification codes are retained as source text where supplied that way. Comment images are retained in the source text form supplied with each record, while Comment voice URL points to an audio attachment when one is available. Published at and Collected at preserve the source timestamps without inferring a timezone. Source note ID and No data retain the collection outcome when a note has no public comment result.
What the results look like
Each normal record represents one publicly visible comment from the selected Xiaohongshu note.
| Comment ID | Comment text | Account name | Published at | Like count | Reply count |
|---|---|---|---|---|---|
| 6a8f8242000000000202b5d5 | 已经是了 都赖国产车 减配吹牛逼 | 四海 | 2026-08-27T08:18:11 | 0 | 0 |
| 6a8f8242000000000202b5d6 | 这款颜色很耐看,通勤也方便 | 小林 | 2026-08-27T08:25:42 | 3 | 1 |
Additional values include account and avatar identifiers, location text, note and comment relationships, image and voice references, recognized speech and on-screen text, collection time, and the no-data marker.
Use cases
- Compare Comment text with Like count and Reply count to identify reactions that generated stronger visible engagement.
- Group Comment text by recurring phrases, then use Published at to see how the discussion changed over time.
- Reconstruct discussion threads with Parent comment ID, Root comment ID, Comment level, and Reply cursor to separate top-level reactions from follow-up conversations.
- Review Account name, Public account ID, IP region, Location cities, and Location provinces to describe visible participant signals without treating them as verified identity data.
適用範囲と境界
Each run accepts one Xiaohongshu note ID and an expected comment count from 1 to 100. Results are returned in complete batches of 10, so the actual count may be rounded up. Only publicly available comments are covered.
- 適している用途
- When you need public comment text and engagement details from a specific Xiaohongshu note
- When you need comment authors, reply relationships, timestamps, and visible location text for analysis
- 適さない用途
- When you need comments from a platform other than Xiaohongshu
- When you need private, deleted, restricted, or login-only comments
失敗時の処理
作者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。
- 1If no comments are returned, verify the note ID and confirm that the note and its comments are publicly visible
- 2Retry later after rate limiting, temporary service unavailability, or a timeout
- 3When the submission outcome is unknown, avoid immediate repeated submissions that could create duplicate tasks
- 4If authentication fails, verify the API Key configured for the execution environment
入力
この App の呼び出しに必要なパラメータで、manifest.json の input.schema から生成されています。
| フィールド | 業務名称 | 型 | 必須 | デフォルト | 列挙値/制約 | 例 | 説明 |
|---|---|---|---|---|---|---|---|
| note_id | Xiaohongshu note ID | string | はい | — | — | 6a6c063d000000002500e938 | The identifier of the Xiaohongshu note whose public comments will be collected. Enter one note ID only, not a keyword or URL. |
| comment_count | Expected comment count | integer | はい | — | 1–100 | 10 | The expected number of comments to collect, from 1 to 100. Results are returned and billed in complete batches of 10, so the actual count may be rounded up. |
出力
1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。
| フィールド | 業務名称 | 型 | 例 | 説明 |
|---|---|---|---|---|
| account_id | Account ID | string | 58f9dce250c4b44bf45e0263 | The Xiaohongshu account identifier associated with the comment author |
| account_name | Account name | string | 四海 | The public display name of the comment author |
| account_public_id | Public account ID | string | xiaohongshu_user_58f9dce2 | The public-facing Xiaohongshu identifier of the comment author |
| accurate_location_cities | Location cities | string | 南京 | City-level location text associated with the comment author when available |
| accurate_location_provinces | Location provinces | string | 江苏 | Province-level location text associated with the comment author when available |
| asr_text | Speech transcript | string | 城市通勤体验分享 | Speech recognition text associated with the referenced note when available |
| avatar_url | Avatar URL | string | https://sns-avatar-qc.xhscdn.com/avatar/61b3eba96564fffada47f01e.jpg?imageView2/2/w/120/format/jpg | The public avatar image URL of the comment author |
| biz_id | Business ID | string | 6a8bfb930000000033020097 | The business identifier carried by the source comment record |
| comment_id | Comment ID | string | 6a8f8242000000000202b5d5 | The stable unique identifier of the Xiaohongshu comment |
| comment_image_url | Comment images | string | [] | The comment image URL collection retained in the source text form |
| comment_level | Comment level | integer | 1 | The source nesting level of the comment |
| comment_text | Comment text | string | 已经是了 都赖国产车 减配吹牛逼 | The text published in the Xiaohongshu comment |
| comment_type_code | Comment type | string | 1 | The source code identifying the comment type |
| comment_voice_url | Comment voice URL | string | https://sns-video-qc.xhscdn.com/comment/voice/6a8f8242000000000202b5d5.m4a | The public voice attachment URL when the comment includes audio |
| content_id | Content ID | string | 6a8bfb930000000033020097 | The identifier of the Xiaohongshu note associated with the comment |
| content_url | Content URL | string | https://www.xiaohongshu.com/explore/6a8bfb930000000033020097 | The public URL of the Xiaohongshu note associated with the comment |
| crawl_time | Collected at | string | 2026-08-27T17:39:26 | The source timestamp when the comment record was collected |
| like_count | Like count | string | 0 | The comment like count at collection time, retained as source text |
| ocr_text | On-screen text | string | 城市通勤 | Text recognized from the referenced note when available |
| parent_comment_id | Parent comment ID | string | 6a8f8242000000000202b5d5 | The identifier of the direct parent comment for a reply |
| publish_ip_region_name | IP region | string | 江苏 | The location text shown for the published comment when available |
| publish_time | Published at | string | 2026-08-27T08:18:11 | The source timestamp when the comment was published |
| reply_count | Reply count | string | 0 | The number of replies at collection time, retained as source text |
| root_comment_id | Root comment ID | string | 6a8f8242000000000202b5d5 | The identifier of the root comment in the reply thread |
| sub_comment_cursor | Reply cursor | string | 0 | The source cursor associated with additional replies when available |
| source_note_id | Source note ID | string | 6a8bfb930000000033020097 | The submitted Xiaohongshu note ID associated with the result record |
| no_data | No data | boolean | false | Whether no public comment data was collected for the source note |
| view_count | View count | string | 0 | The view count associated with the referenced note at collection time, retained as source text |
レコード Schema
出力はレコード単位で 1 件ずつ返されます。 detail.output.idFieldHint
{
"type": "object",
"properties": {
"account_id": {
"type": "string",
"title": "Account ID",
"description": "The Xiaohongshu account identifier associated with the comment author",
"prefill": "58f9dce250c4b44bf45e0263"
},
"account_name": {
"type": "string",
"title": "Account name",
"description": "The public display name of the comment author",
"prefill": "四海"
},
"account_public_id": {
"type": "string",
"title": "Public account ID",
"description": "The public-facing Xiaohongshu identifier of the comment author",
"prefill": "xiaohongshu_user_58f9dce2"
},
"accurate_location_cities": {
"type": "string",
"title": "Location cities",
"description": "City-level location text associated with the comment author when available",
"prefill": "南京"
},
"accurate_location_provinces": {
"type": "string",
"title": "Location provinces",
"description": "Province-level location text associated with the comment author when available",
"prefill": "江苏"
},
"asr_text": {
"type": "string",
"title": "Speech transcript",
"description": "Speech recognition text associated with the referenced note when available",
"prefill": "城市通勤体验分享"
},
"avatar_url": {
"type": "string",
"title": "Avatar URL",
"description": "The public avatar image URL of the comment author",
"prefill": "https://sns-avatar-qc.xhscdn.com/avatar/61b3eba96564fffada47f01e.jpg?imageView2/2/w/120/format/jpg"
},
"biz_id": {
"type": "string",
"title": "Business ID",
"description": "The business identifier carried by the source comment record",
"prefill": "6a8bfb930000000033020097"
},
"comment_id": {
"type": "string",
"title": "Comment ID",
"description": "The stable unique identifier of the Xiaohongshu comment",
"prefill": "6a8f8242000000000202b5d5"
},
"comment_image_url": {
"type": "string",
"title": "Comment images",
"description": "The comment image URL collection retained in the source text form",
"prefill": "[]"
},
"comment_level": {
"type": "integer",
"title": "Comment level",
"description": "The source nesting level of the comment",
"prefill": 1
},
"comment_text": {
"type": "string",
"title": "Comment text",
"description": "The text published in the Xiaohongshu comment",
"prefill": "已经是了 都赖国产车 减配吹牛逼"
},
"comment_type_code": {
"type": "string",
"title": "Comment type",
"description": "The source code identifying the comment type",
"prefill": "1"
},
"comment_voice_url": {
"type": "string",
"title": "Comment voice URL",
"description": "The public voice attachment URL when the comment includes audio",
"prefill": "https://sns-video-qc.xhscdn.com/comment/voice/6a8f8242000000000202b5d5.m4a"
},
"content_id": {
"type": "string",
"title": "Content ID",
"description": "The identifier of the Xiaohongshu note associated with the comment",
"prefill": "6a8bfb930000000033020097"
},
"content_url": {
"type": "string",
"title": "Content URL",
"description": "The public URL of the Xiaohongshu note associated with the comment",
"prefill": "https://www.xiaohongshu.com/explore/6a8bfb930000000033020097"
},
"crawl_time": {
"type": "string",
"title": "Collected at",
"description": "The source timestamp when the comment record was collected",
"prefill": "2026-08-27T17:39:26"
},
"like_count": {
"type": "string",
"title": "Like count",
"description": "The comment like count at collection time, retained as source text",
"prefill": "0"
},
"ocr_text": {
"type": "string",
"title": "On-screen text",
"description": "Text recognized from the referenced note when available",
"prefill": "城市通勤"
},
"parent_comment_id": {
"type": "string",
"title": "Parent comment ID",
"description": "The identifier of the direct parent comment for a reply",
"prefill": "6a8f8242000000000202b5d5"
},
"publish_ip_region_name": {
"type": "string",
"title": "IP region",
"description": "The location text shown for the published comment when available",
"prefill": "江苏"
},
"publish_time": {
"type": "string",
"title": "Published at",
"description": "The source timestamp when the comment was published",
"prefill": "2026-08-27T08:18:11"
},
"reply_count": {
"type": "string",
"title": "Reply count",
"description": "The number of replies at collection time, retained as source text",
"prefill": "0"
},
"root_comment_id": {
"type": "string",
"title": "Root comment ID",
"description": "The identifier of the root comment in the reply thread",
"prefill": "6a8f8242000000000202b5d5"
},
"sub_comment_cursor": {
"type": "string",
"title": "Reply cursor",
"description": "The source cursor associated with additional replies when available",
"prefill": "0"
},
"source_note_id": {
"type": "string",
"title": "Source note ID",
"description": "The submitted Xiaohongshu note ID associated with the result record",
"prefill": "6a8bfb930000000033020097"
},
"no_data": {
"type": "boolean",
"title": "No data",
"description": "Whether no public comment data was collected for the source note",
"prefill": false
},
"view_count": {
"type": "string",
"title": "View count",
"description": "The view count associated with the referenced note at collection time, retained as source text",
"prefill": "0"
}
},
"required": [],
"additionalProperties": false
}連携方法
この App は MCP、API、SDK、ファイルエクスポートのいずれでも連携でき、どのチャネルも同じ能力と料金を共有します。すべてのリクエストは Authorization: Bearer ヘッダーで認証し、認証情報には API Key(長期有効。Data Hub コンソールで作成)を使用します。MCP クライアントは OAuth によるキー不要のログインにも対応しています。CLI や Skill など、さらに多くの連携方法も準備中です。
MCP(Model Context Protocol)を使うと、Claude や Cursor などの AI クライアントからこの App を直接呼び出せます。クライアントと認証方式を選び、下の設定をコピーしてください。
クライアント設定
Bearer の後の値を長期有効な API Key に置き換えてください。あらゆるクライアント、CI、ヘッドレス環境で利用できます。
{
"mcpServers": {
"meme_today__xiaohongshu-note-comments": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-note-comments",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}AI に設定を任せる
設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します(プロンプトは AI があなたに API Key を尋ねる形になっているため、認証情報がチャット履歴や共有設定に残りません)。
detail.access.mcp.composeHint
料金
正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。 10 件を 1 つの課金単位とし、端数は 10 件に切り上げて課金されます。
返される件数にかかわらず、実行の送信 1 回ごとに課金されます。
複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。
Credits を確認今すぐ試す
パラメータを入力して実行してください。結果は実際の呼び出しによるものです。