After a spreadsheet-import tutorial, viewers keep saying that it does not work for them. Should the next video repeat everything or explain one missing step? Recover the actual problem before planning the follow-up.
Connect comments to the demonstrated version
Verify the video and software context. Comment requests use bv_id, while the bound detail request uses aid. Preserve page coverage and lookup time. A recent comment on an older tutorial may refer to a different interface. Treat an unstated version as information to request, not a detail to invent.
Find what vague reports leave out
Group remarks by the problems actually present, such as importing, formatting or saving. Record the step, input and error when stated. For comments with existing answers, retrieve replies using rpid and check whether the author already resolved the issue.
Plan footage from a question table
Useful columns are source, blocked action, environment, existing answer, reproducibility and footage needed. A specific view of an import-settings window is more actionable than “explain better.” Combine similar questions without losing different environments. Repetition within the sample does not establish a failure rate for all viewers.
Reproduce before recommending a fix
Try the most consequential issues using your own test material. AI can group descriptions but cannot establish causes or invent verified repairs. Turn incomplete reports into clarification questions. The output is a set of concrete demonstrations and unresolved conditions that can make the next tutorial more useful.
Requests used in this project
- Get comments on the specified video:https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_comments · Documentation
- Get reply to the specified comment:https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_comment_reply · Documentation
- Get single video detail:https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_detail · Documentation
Request URL and parameters
GET https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_comments
| Parameter | Type | Required | Meaning |
|---|---|---|---|
bv_id |
string | Yes | Video id |
pn |
integer | No | Page number |
Run the Python example
Install requests and set TRMESH_API_TOKEN in your environment. Replace the sample identifiers with the public object you intend to inspect. Example IDs may no longer be available.
import os
import requests
# Read your own developer key from the server environment.
url = "https://api.trmesh.com/openapi/api/v1/bilibili/web/fetch_video_comments"
params = {
"bv_id": "BV1M1421t7hT"
}
response = requests.get(
url, params=params, timeout=30,
headers={"Authorization": f"Bearer {os.environ['TRMESH_API_TOKEN']}"},
)
response.raise_for_status()
payload = response.json()
print(payload) # Inspect the actual response before mapping fields
Endpoint documentation · Free profile tool
API calls use your TRMesh account allowance. Check the endpoint price before running a script.