Provide one Bilibili video BV ID or av ID and an expected comment count to receive public comments, user details, engagement, and timestamps
Weibo Comment Collector
Retrieve public Weibo comments with user, engagement, and time information from a post ID, user ID, and target comment count
Overview
Weibo comments capture direct reactions to content, people, and topics. This App retrieves public comments for a known Weibo post and user, then organizes comment text, user information, engagement data, reply relationships, and timestamps into individual records for filtering and analysis.
Compared with manual browsing, the result preserves links between comments, the Weibo content, parent comments, and root comments. It also returns likes, child-comment counts, user names, and publicly shown locations. These fields support content review, audience observation, and sentiment analysis.
Data notes
The data comes from publicly visible comments on the specified Weibo post. Comment ID identifies a comment record. Comment text may be accompanied by OCR or speech-recognition text; image and video URLs remain in the source format. Parent and root comment IDs help reconstruct reply relationships. Like counts, child-comment counts, follower counts, and engagement values reflect the collected snapshot and may change later. Publish and collection times remain in the source time format without additional timezone conversion. Private, deleted, hidden, or inaccessible comments are outside the coverage.
What the results look like
Each record represents one public Weibo comment:
| Comment ID | User name | Comment text | Like count | Publish time |
|---|---|---|---|---|
| 5358366253648038 | Weibo Search | A representative public comment | 0 | 2026-10-26T20:25:31 |
| 5361896420000001 | Example user | This content is useful for reference | 3 | 2026-10-26T20:30:00 |
Additional fields include content ID, parent comment ID, root comment ID, child-comment count, user avatar, IP location, and collection time.
Use cases
- Review content reception with Comment text and Like count.
- Analyze discussion structure with Comment ID, Parent comment ID, Root comment ID, and Child comment count.
- Observe audiences by grouping User name and IP location and tracking Publish time.
Scope and boundaries
One Weibo post per task; the App tries to return the requested number of public comments, but fewer may be returned when public data is insufficient.
- Good for
- When detailed public comments for one known Weibo post are needed
- When comment text, users, engagement, or reply relationships must be analyzed
- Do not use for
- When Weibo posts must be discovered by keyword; this App handles known post IDs only
- When private, deleted, hidden, or inaccessible comments are required; only public data is covered
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1For empty results, verify the post ID and user ID and confirm that the post is public and has comments
- 2Retry later for rate limits, timeouts, or temporary service unavailability
- 3Fix authentication, permission, or task-context configuration before retrying those errors
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- Weibo post ID
post_idRequiredstringNumeric Weibo post ID; do not enter a post URLExample5358366199387071 - Weibo user ID
user_idRequiredstringNumeric ID of the user who owns the Weibo postExample4062241162 - Target comment count
comment_countRequiredintegerTarget rather than strict upper bound; fewer may be returned when public data is insufficientRange1–Example10
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Account text
accountstringOriginal account text returned by the source - Account description
account_descriptionstringOriginal account description returned by the sourceExample微博智搜AI账号 - User ID
account_idstringOriginal user id returned by the sourceExample7892270010 - User name
account_namestringOriginal user name returned by the sourceExample微博智搜
Sample data
Generated from output.schema. Fields without a sample value use structural placeholders.
{
"account": "<account>",
"account_description": "微博智搜AI账号",
"account_id": "7892270010",
"account_name": "微博智搜",
"account_short_id": "<account_short_id>",
"accurate_location_cities": "<accurate_location_cities>",
"accurate_location_provinces": "<accurate_location_provinces>",
"asr_text": "<asr_text>",
"avatar_url": "https://tvax2.sinaimg.cn/crop.0.0.1080.1080.1024/008C79XAly8i5grzh416kj30u00u0t8z.jpg?KID=imgbed,tva&Expires=1793946249&ssig=DrC9GqcgOx",
"biz_id": "5358366199387071&&&&4062241162",
"clean_update_time": "2026-11-06T11:27:21.254",
"collect_count": "<collect_count>",
"comment_id": "5358366253648038",
"comment_image_list": "<comment_image_list>",
"comment_image_url_list": "<comment_image_url_list>",
"comment_text": "太能打了!田栩宁《ELLE》八月刊以创刊38年男星最高规格单人四封亮相,邀封+MaisonMargiela高定全球首穿,开售13小时25分登顶五大刊榜首,24小时销售额超3235万、销量46.2万本,48小时破3300万,刷新该刊历史纪录。...查看全部戳-><a target=\"_blank\" href=\"https://ai.s.weibo.com/api/chat/pm/private_comment.json?ext=%7B%22mid%22%3A%20%225358366199387071%22%2C%20%22mid_uid%22%3A%204062241162%2C%20%22verification_page_id%22%3A%20%22%22%2C%20%22cid%22%3A%20%22%22%2C%20%22comment_page_id%22%3A%20%222329644b108e82a6513125f00c8487e488f357%22%2C%20%22is_positivity%22%3A%202%2C%20%22ts%22%3A%201793017531%2C%20%22reply_type%22%3A%2016%7D\"><img class=\"icon-link\" title=\"http://t.cn/AXjXj0V7\" src=\"https://h5.sinaimg.cn/upload/2015/09/25/3/timeline_card_small_web_default.png\"/>微博智搜</a>",
"comment_type": "1",
"comment_url": "<comment_url>",
"comment_video_url_list": "<comment_video_url_list>",
"content_id": "5358366199387071",
"crawl_time": "2026-11-06T11:24:12.428",
"cur_id": "6aed491906d05663663fa82b",
"custom_verify": "新浪微博智搜官方账号",
"data_source_type": "<data_source_type>",
"etl_updated_time": "2026-11-06T11:27:21",
"ext_info": "{\"bizId\": \"5358366199387071&&&&4062241162\", \"groupId\": \"224\", \"jobType\": \"Comment\", \"oldId\": \"[REDACTED]\", \"platform\": \"weibo\", \"table\": \"weibo_comment_web\", \"table_type\": \"2\", \"trace_id\": \"[REDACTED]\"}",
"fans": "4797618",
"form_type": "<form_type>",
"from_url": "<from_url>",
"ip_location": "北京",
"keyword": "<keyword>",
"like_count": "0",
"ocr_text": "<ocr_text>",
"parent_comment_id": "5358366253648038",
"partition_day": "2026-11-06",
"publish_time": "2026-10-26T20:25:31",
"repost_count": "<repost_count>",
"root_comment_id": "5358366253648038",
"source_level": "<source_level>",
"source_record_id": "6aed491906d05663663fa82b",
"source_unique_id": "<source_unique_id>",
"sr_updated_time": "2026-11-06T11:27:21",
"status": "<status>",
"sub_comment_count": "0",
"task_item": "5358366199387071&&&&4062241162",
"no_data": false,
"verify_type": "<verify_type>",
"view_count": "<view_count>",
"wb_num": "1160"
}Integration
This App can be integrated via MCP, API, SDK, or file export. All channels share the same capabilities and pricing. Every request authenticates with the Authorization: Bearer header using an API key (long-lived, created in the Data Hub Console); MCP clients can also sign in with OAuth, no key required. More options such as CLI and Skill are on the way. This App runs asynchronously and can be canceled midway: After you cancel, the run stops. Records already delivered are kept and billed.
With the MCP (Model Context Protocol), you can call this App directly from AI clients like Claude and Cursor. Pick your client and auth mode, then copy the config below.
Client config
Replace the value after Bearer with your long-lived API key. Works in any client, CI, or headless environment.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/weibo-comment",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Let AI set it up for you
Don't want to edit configs by hand? Copy the install prompt and paste it into any AI client. It will complete the setup its own way. (By default it guides you through signing in, and never asks you to send your API key in the chat.)
detail.access.mcp.composeHint
Pricing
Charged once per submitted run, regardless of how many records are returned.
Charged by the number of records successfully returned. Failed runs are not charged. Billed in units of 10 records; any partial unit is rounded up to 10 records.
Multiple billing events accumulate independently. See each item for details. Failed runs are not charged.
View creditsTry it now
Fill in the parameters and run. Results come from a real call.