Xiaohongshu Account Content List

Collect public Xiaohongshu account content with account identifiers, titles, and collection timestamps

概要

Xiaohongshu account content offers a direct view of what an account publishes and how its public activity changes over time. This app turns the visible content associated with one account into a consistent record set, preserving the identifiers and timestamps that are useful for research, monitoring, and content planning.

The collection is useful when a profile page is too narrow a view. It keeps the account relationship, content identity, displayed title, publication time, and collection time together so teams can build an inventory, compare collection snapshots, and trace which public posts belong to a monitored account.

Data notes

The data comes from the public content list associated with the selected Xiaohongshu account. Records are returned from the source list and duplicate content IDs are removed across collected pages. Account identifiers, business identifiers, titles, and timestamps retain the source values; a source value can be unavailable and appear empty. Publication and collection timestamps are preserved as supplied, without inferring a timezone. Private, deleted, restricted, and login-only content is outside the coverage.

What the results look like

Each record represents one piece of public Xiaohongshu account content.

Content ID	Content title	Published at	Collected at	No data
6a86bf44000000002403fd59	去看了下智界RX，价格有点超预期...	2026-08-20T16:48:04	2026-08-27T10:25:46	No
6a844ebe00000000050306cf	鸿蒙系统怎么设置倾斜手机壁纸变色？	2026-08-18T20:23:26	2026-08-27T10:25:46	No

Additional values include Account ID, Account unique ID, Business ID, Source account item, and the source no-data marker.

Use cases

Build a publishing inventory by grouping Content ID and Content title under Account ID, then compare Published at across repeated collections.
Monitor posting cadence by counting records by Published at and checking whether the visible activity of an account is increasing or slowing.
Trace collection freshness by comparing Published at with Collected at when reviewing a monitored account.
Separate empty-result outcomes from normal content by checking No data together with Source account item.

適用範囲と境界

Each run processes one Xiaohongshu account ID and accepts an expected count from 1 to 20,000. Results are returned in complete batches of 20, so the actual count may be rounded up. Up to 1,000 result pages are protected per run, and only publicly visible content is covered.

適している用途
When you need a public content list for a specific Xiaohongshu account
When you need post identifiers, titles, publication times, and collection times for content analysis

適さない用途
When you need private, deleted, restricted, or login-only content
When you need an instant single-record lookup rather than a collected list

失敗時の処理

作者が宣言した失敗時と再試行の動作です。連携時にはシステムプロンプトに含めることをおすすめします。

1If no data is returned, verify the account ID and confirm that the account has publicly visible content
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 から生成されています。

フィールド	業務名称	型	必須	デフォルト	列挙値／制約	例	説明
account_id	Xiaohongshu account ID	string	はい	—	—	6366a311000000001f01fd6c	The Xiaohongshu account ID whose public content should be collected. Enter 1 to 512 characters.
crawl_num	Expected content count	integer	はい	—	1–20000	20	The expected number of content records to collect. Results are returned in complete batches of 20, so the actual count may be rounded up; values above 20,000 are not accepted.

出力

1 件のレコードのフィールド構造で、manifest.json の output.schema から生成されています。

フィールド	業務名称	型	例	説明
account_id	Account ID	string	6366a311000000001f01fd6c	The Xiaohongshu account identifier associated with the content record; the source may return null.
account_unique_id	Account unique ID	string	xiaohongshu_account_example	The account's unique identifier supplied by the source; it may be null when unavailable.
biz_id	Business ID	string	6366a311000000001f01fd6c	The business identifier carried by the source record; it may be null.
content_id	Content ID	string	6a86bf44000000002403fd59	The content identifier used to distinguish records across result pages; it may be null in source data.
content_title	Content title	string	去看了下智界RX，价格有点超预期...	The title or displayed text of the public Xiaohongshu content; it may be null.
crawl_time	Collected at	string	2026-08-27T10:25:46	The source timestamp when the content was collected, without an inferred timezone; it may be null.
publish_time	Published at	string	2026-08-20T16:48:04	The source timestamp when the content was published, without an inferred timezone; it may be null.
source_item	Source account item	string	6366a311000000001f01fd6c	The account item associated with the result, copied from the task metadata.
no_data	No data	boolean	false	Whether the task metadata marks this account result as having no public data.

レコード Schema

出力はレコード単位で 1 件ずつ返されます。 detail.output.idFieldHint

output.schema

{
  "type": "object",
  "properties": {
    "account_id": {
      "type": "string",
      "title": "Account ID",
      "description": "The Xiaohongshu account identifier associated with the content record; the source may return null.",
      "prefill": "6366a311000000001f01fd6c"
    },
    "account_unique_id": {
      "type": "string",
      "title": "Account unique ID",
      "description": "The account's unique identifier supplied by the source; it may be null when unavailable.",
      "prefill": "xiaohongshu_account_example"
    },
    "biz_id": {
      "type": "string",
      "title": "Business ID",
      "description": "The business identifier carried by the source record; it may be null.",
      "prefill": "6366a311000000001f01fd6c"
    },
    "content_id": {
      "type": "string",
      "title": "Content ID",
      "description": "The content identifier used to distinguish records across result pages; it may be null in source data.",
      "prefill": "6a86bf44000000002403fd59"
    },
    "content_title": {
      "type": "string",
      "title": "Content title",
      "description": "The title or displayed text of the public Xiaohongshu content; it may be null.",
      "prefill": "去看了下智界RX，价格有点超预期..."
    },
    "crawl_time": {
      "type": "string",
      "title": "Collected at",
      "description": "The source timestamp when the content was collected, without an inferred timezone; it may be null.",
      "prefill": "2026-08-27T10:25:46"
    },
    "publish_time": {
      "type": "string",
      "title": "Published at",
      "description": "The source timestamp when the content was published, without an inferred timezone; it may be null.",
      "prefill": "2026-08-20T16:48:04"
    },
    "source_item": {
      "type": "string",
      "title": "Source account item",
      "description": "The account item associated with the result, copied from the task metadata.",
      "prefill": "6366a311000000001f01fd6c"
    },
    "no_data": {
      "type": "boolean",
      "title": "No data",
      "description": "Whether the task metadata marks this account result as having no public data.",
      "prefill": false
    }
  },
  "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 config

{
  "mcpServers": {
    "meme_today__xiaohongshu-account-list": {
      "type": "http",
      "url": "https://mcp-v2.octoparse.com?pin=meme_today/xiaohongshu-account-list",
      "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
    }
  }
}

自分の API Keys を表示 →

AI に設定を任せる

設定を手作業で編集したくない場合は、インストールプロンプトをコピーして任意の AI クライアントに貼り付けてください。AI が自分のやり方でセットアップを完了します（プロンプトは AI があなたに API Key を尋ねる形になっているため、認証情報がチャット履歴や共有設定に残りません）。

detail.access.mcp.composeHint

料金

20 returned records

正常に返されたレコードの件数に応じて課金されます。失敗した実行には課金されません。 20 件を 1 つの課金単位とし、端数は 20 件に切り上げて課金されます。

$0.01/ 20 件

Per task submitted

返される件数にかかわらず、実行の送信 1 回ごとに課金されます。

$0.0001/ 回

複数の課金イベントはそれぞれ独立して累計されます。詳細は各項目をご覧ください。失敗した実行には課金されません。

Credits を確認

今すぐ試す

パラメータを入力して実行してください。結果は実際の呼び出しによるものです。

サンプル

パラメータは送信前に input.schema で検証されます

Xiaohongshu account IDaccount_id*The Xiaohongshu account ID whose public content should be collected. Enter 1 to 512 characters.

Expected content countcrawl_num*The expected number of content records to collect. Results are returned in complete batches of 20, so the actual count may be rounded up; values above 20,000 are not accepted.

まず必須パラメータを入力してください

$0.01 / 20 件から