Retrieve public Weibo comments with user, engagement, and time information from a post ID, user ID, and target comment count
Bilibili Video Comments
Provide one Bilibili video BV ID or av ID and an expected comment count to receive public comments, user details, engagement, and timestamps
Overview
Bilibili Video Comments turns the public discussion of one specified video into a structured dataset for analysis. Provide a video BV ID or av ID and an expected comment count, then receive comment text, author details, engagement, reply relationships, and timestamps after the asynchronous task completes.
Each record represents one comment returned by the interface. Account extensions, image URL lists, and other extended fields remain in the original JSON text form. Count fields remain in the original text form returned by the interface, and timestamps preserve the interface values. Results are returned 20 comments per page and billed in batches of 20 comments.
Data notes
The data covers public comments that the interface can return for the specified Bilibili video identified by a BV ID or av ID. It includes comment text, author details, avatar, verification, location, engagement counts, comment and video links, reply relationships, and task metadata. Some comments may have no author extensions, location, media, engagement, or OCR values; those fields are empty.
What the results look like
Each record represents one public comment from the selected video:
| Comment ID | Comment text | Account name | Video ID | Published at | Like count |
|---|---|---|---|---|---|
| 307532404624 | Public comment text returned by the interface | Public account name | av117566357899570 | 2026-06-30T20:41:53 | 46 |
Use cases
- Analyze audience reactions with Comment text, Published at, Like count, and Reply count.
- Describe publicly visible participants with Account name, Avatar URL, Verification type, and location fields.
- Reconstruct reply relationships with Comment ID, Parent comment ID, and Root comment ID.
- Build traceable content review records with Video ID, Video title, Comment URL, and Collected at.
Scope and boundaries
Collect public comments from one known Bilibili video per run. The video ID may use BV format or av format; the requested count is supplied as input, results are returned 20 comments per page, and billing is in batches of 20 comments. Actual results depend on public availability and task processing.
- Good for
- When you need public comment details from a specific Bilibili video
- When you need to analyze comment text, authors, engagement, or reply relationships
- Do not use for
- When you need to discover Bilibili videos by keyword; this App requires a known BV ID or av ID
- When you need private, deleted, restricted, or login-only comments; this App covers only data returned by the public collection interface
Failure handling
Failure and retry behavior declared by the developer. We recommend including it in your system prompt when integrating.
- 1If no results are returned, verify the BV ID or av ID, public video access, and whether comments exist
- 2Retry later after rate limiting, timeout, or temporary service unavailability
- 3For authentication, permission, or task-context errors, check the execution environment credential and configuration before retrying
Input
Parameters required to call this App, generated from the input.schema in manifest.json.
- Video ID (BV or av format)
video_idRequiredstringThe ID of one Bilibili video whose public comments should be collected. Supports BV IDs such as BV1gbKZ6cE52 and av IDs such as av117566357899570. Enter the ID only, not a URL or search keyword.ExampleBV1gbKZ6cE52 - Expected comment count
comment_countRequiredintegerThe requested number of comments. Results are returned 20 comments per page and billed in batches of 20; actual results depend on public comments and task processing.Range1–Example20
Output
Field structure of a single record, generated from the output.schema in manifest.json.
- Account ID
account_idstringThe Bilibili account identifier of the comment author - Account name
account_namestringThe author display name shown publicly - Raw account information
account_raw_textstringRaw JSON text containing extended author information - Short account ID
account_short_idstringThe author short account identifier when available
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/bilibili-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 by the number of records successfully returned. Failed runs are not charged. Billed in units of 20 records; any partial unit is rounded up to 20 records.
Charged once per submitted run, regardless of how many records are returned.
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.