WeChat動画アカウントのキーワードと最大件数を指定すると、一致する公開動画、投稿アカウント、反応数、日時を取得します。
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 から生成されています。
- Xiaohongshu note ID
note_id必須stringThe identifier of the Xiaohongshu note whose public comments will be collected. Enter one note ID only, not a keyword or URL.例6a6c063d000000002500e938 - Expected comment count
comment_count必須integerThe 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–100例10
出力
1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。
- Account ID
account_idstringThe Xiaohongshu account identifier associated with the comment author例58f9dce250c4b44bf45e0263 - Account name
account_namestringThe public display name of the comment author例四海 - Public account ID
account_public_idstringThe public-facing Xiaohongshu identifier of the comment author例xiaohongshu_user_58f9dce2 - Location cities
accurate_location_citiesstringCity-level location text associated with the comment author when available例南京
サンプルデータ
output.schema から生成したサンプルです。サンプル値のないフィールドには構造上のプレースホルダーを使用しています。
{
"account_id": "58f9dce250c4b44bf45e0263",
"account_name": "四海",
"account_public_id": "xiaohongshu_user_58f9dce2",
"accurate_location_cities": "南京",
"accurate_location_provinces": "江苏",
"asr_text": "城市通勤体验分享",
"avatar_url": "https://sns-avatar-qc.xhscdn.com/avatar/61b3eba96564fffada47f01e.jpg?imageView2/2/w/120/format/jpg",
"biz_id": "6a8bfb930000000033020097",
"comment_id": "6a8f8242000000000202b5d5",
"comment_image_url": "[]",
"comment_level": 1,
"comment_text": "已经是了 都赖国产车 减配吹牛逼",
"comment_type_code": "1",
"comment_voice_url": "https://sns-video-qc.xhscdn.com/comment/voice/6a8f8242000000000202b5d5.m4a",
"content_id": "6a8bfb930000000033020097",
"content_url": "https://www.xiaohongshu.com/explore/6a8bfb930000000033020097",
"crawl_time": "2026-08-27T17:39:26",
"like_count": "0",
"ocr_text": "城市通勤",
"parent_comment_id": "6a8f8242000000000202b5d5",
"publish_ip_region_name": "江苏",
"publish_time": "2026-08-27T08:18:11",
"reply_count": "0",
"root_comment_id": "6a8f8242000000000202b5d5",
"sub_comment_cursor": "0",
"source_note_id": "6a8bfb930000000033020097",
"no_data": false,
"view_count": "0"
}連携方法
この App は MCP、API、SDK、ファイルエクスポートのいずれでも連携でき、どのチャネルも同じ能力と料金を共有します。すべてのリクエストは Authorization: Bearer ヘッダーで認証し、認証情報には API Key(長期有効。Data Hub コンソールで作成)を使用します。MCP クライアントは OAuth によるキー不要のログインにも対応しています。CLI や Skill など、さらに多くの連携方法も準備中です。 この App は非同期で実行され、途中でキャンセルできます:キャンセル後、実行は停止します。納品済みのレコードは保持され、課金対象になります。
MCP(Model Context Protocol)を使うと、Claude や Cursor などの AI クライアントからこの App を直接呼び出せます。クライアントと認証方式を選び、下の設定をコピーしてください。
クライアント設定
Bearer の後の値を長期有効な API Key に置き換えてください。あらゆるクライアント、CI、ヘッドレス環境で利用できます。
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-note-comments",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}AI に設定を任せる
設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します(デフォルトではログインを案内し、API Key をチャットに送るよう求めることはありません)。
detail.access.mcp.composeHint
料金
正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。 10 件を 1 つの課金単位とし、端数は 10 件に切り上げて課金されます。
返される件数にかかわらず、実行の送信 1 回ごとに課金されます。
複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。
Credits を確認今すぐ試す
パラメータを入力して実行してください。結果は実際の呼び出しによるものです。