Recopila comentarios públicos, datos de usuarios, interacción y marcas de tiempo de un vídeo de Bilibili mediante su ID BV o av
Weibo Comment Collector
Retrieve public Weibo comments with user, engagement, and time information from a post ID, user ID, and target comment count
Original · en-USVolver a la traducción
Descripción general
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.
Alcance y límites
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.
- Adecuada para
- When detailed public comments for one known Weibo post are needed
- When comment text, users, engagement, or reply relationships must be analyzed
- No usar para
- 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
Gestión de fallos
Comportamiento de fallos y reintentos declarado por el desarrollador. Recomendamos incluirlo en tu prompt del sistema al integrar.
- 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
Entrada
Parámetros necesarios para llamar a esta App, generados a partir del input.schema del manifest.json.
- Weibo post ID
post_idObligatoriostringNumeric Weibo post ID; do not enter a post URLEjemplo5358366199387071 - Weibo user ID
user_idObligatoriostringNumeric ID of the user who owns the Weibo postEjemplo4062241162 - Target comment count
comment_countObligatoriointegerTarget rather than strict upper bound; fewer may be returned when public data is insufficientRango1–Ejemplo10
Salida
Estructura de campos de un único registro, generada a partir del output.schema del manifest.json.
- Account text
accountstringOriginal account text returned by the source - Account description
account_descriptionstringOriginal account description returned by the sourceEjemplo微博智搜AI账号 - User ID
account_idstringOriginal user id returned by the sourceEjemplo7892270010 - User name
account_namestringOriginal user name returned by the sourceEjemplo微博智搜
Datos de ejemplo
Generado a partir de output.schema. Los campos sin valor de ejemplo usan marcadores de estructura.
{
"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"
}Integración
Esta App se puede integrar mediante MCP, API, SDK o exportación de archivos — todos los canales comparten las mismas capacidades y precios. Cada solicitud se autentica con la cabecera Authorization: Bearer usando una API Key (de larga duración, creada en la consola de Data Hub); los clientes MCP también pueden iniciar sesión con OAuth sin clave. Más opciones como CLI y Skill están en camino. Esta App se ejecuta de forma asíncrona y se puede cancelar a mitad de camino: Tras la cancelación, la ejecución se detiene. Los registros ya entregados se conservan y se facturan.
Con MCP (Model Context Protocol) puedes llamar a esta App directamente desde clientes de IA como Claude y Cursor. Elige tu cliente y el modo de autenticación, y copia la configuración de abajo.
Configuración del cliente
Sustituye el valor tras Bearer por tu API Key de larga duración. Funciona en cualquier cliente, CI o entorno sin interfaz.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/weibo-comment",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Deja que la IA lo configure por ti
¿No quieres editar configuraciones a mano? Copia el prompt de instalación y pégalo en cualquier cliente de IA: completará la configuración a su manera. (De forma predeterminada te guía para iniciar sesión y nunca te pide que envíes tu API Key en el chat.)
detail.access.mcp.composeHint
Precios
Se cobra una vez por cada ejecución enviada, independientemente del número de registros devueltos.
Se cobra según el número de registros devueltos correctamente. Las ejecuciones fallidas no se cobran. Se factura en unidades de 10 registros; cualquier unidad parcial se redondea a 10 registros.
Los distintos eventos de facturación se acumulan de forma independiente. Consulta cada elemento para más detalles. Las ejecuciones fallidas no se cobran.
Ver créditosPruébalo ahora
Rellena los parámetros y ejecuta — los resultados provienen de una llamada real.