> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# How do I clarify “it did not work” in Kuaishou comments before summarizing the issue?

> Read selected-post comments, expand relevant root replies, preserve conditions and relationships, then choose further reading or follow-up.

**First find which step and which conditions the comment is about, then read that comment's replies with `kuaishou.app.fetch_video_sub_comments`; read more root comments with `kuaishou.app.fetch_video_comment` only when you need other viewers' experiences.** “It did not work” is a lead to clarify, not a complete diagnosis.

For example, a cooking tutorial may prompt questions about substitutions, cookware or preparation order. The author may already have explained the step in a reply, or another viewer may have pointed out that the commenter used a different ingredient. Keep the parent comment and the original wording for the content team.

## Read an initial comment batch

Use the verified post identifier as `photo_id` for `kuaishou.app.fetch_video_comment`, starting with empty `pcursor`:

```json
{
  "action": "kuaishou.app.fetch_video_comment",
  "params": {"photo_id": "<confirmed_photo_id>", "pcursor": ""}
}
```

Send the request to `POST https://api.beatapi.io/v1/social-data/call` with BeatAPI Bearer authentication. Save the post source, the action, the inputs, the actual time, the response and the request ID. To reclassify comments later, reuse the saved response instead of requesting again.

## Which discussion needs replies?

| Root-comment situation                      | Material to add                                              |
| ------------------------------------------- | ------------------------------------------------------------ |
| An unsuccessful attempt without conditions  | Context, author questions and subsequent explanation         |
| An apparently omitted preparation step      | Replies and the original demonstration when needed           |
| A correction about ingredients or equipment | The statement being corrected and author confirmation        |
| General agreement or campaign participation | Retain as background or exclude without expanding everything |

With a verified root-comment ID, read the root comment's replies with `kuaishou.app.fetch_video_sub_comments`:

```json
{
  "action": "kuaishou.app.fetch_video_sub_comments",
  "params": {"photo_id": "<confirmed_photo_id>", "root_comment_id": "<confirmed_root_comment_id>", "pcursor": "", "count": 8}
}
```

`root_comment_id` identifies the root comment, not the post or a user. In `kuaishou.app.fetch_video_sub_comments`, `count` defaults to 8 with a documented range of 1–20. `kuaishou.app.fetch_video_comment` has no `count` input.

The output contract does not fix the paths of the comment array, the comment text, the identifiers or the continuation cursor. Read those paths from your saved responses; do not assume `data.comments` or a uniform `next_cursor`.

## How do you avoid joining unrelated pages?

Save the root-comment cursor separately from each root comment's reply cursor. To continue a branch, pass the cursor that the same branch returned. When you change the post, the root comment or the action, start from that request's first page; do not reuse a cursor from another request because the field has the same name.

Suppose you read page one of the comments on post A and opened the replies under comment C01. Save two progress rows:

| What you read                | How to resume                                                                                        |
| ---------------------------- | ---------------------------------------------------------------------------------------------------- |
| Top-level comments on post A | Use post A's `photo_id` and the top-level comment cursor from that page                              |
| Replies under comment C01    | Use the same `photo_id`, the actual `root_comment_id` for C01, and the cursor from that reply thread |

A creator's post list also uses `pcursor`. Save the creator post list's cursor and `sort` in a separate row, so you can return to where you left off selecting posts.

When the cursor is missing or repeats, a request fails or you reach the planned page count, stop and record the scope read and the stopping reason. Record the displayed comment total, the requested `count` and the number of comments actually read as three separate numbers.

## How do you hand off answerable questions?

For each comment, keep the wording, the post and comment source, the parent relationship, the known conditions, the missing information, your interpretation and the next step. Label each comment as a question, a reported experience, an author addition or a correction.

A question about smaller cookware is a question about conditions. An author reply that explains an earlier step may complete the instructions. Group a “Same here” reply only when the parent comment makes the context clear. Attach representative excerpts and conditions to each theme.

When the same comment appears on several pages, match the comment by ID and keep each observation. When you count supporting comments and distinct posts, note which replies belong to the same conversation; replies in one thread are not independent users.

For the assistant:

> Read this cooking post's comments for preparation and condition questions. Expand ambiguous discussions, preserving parents and author explanations. List wording, conditions, answerable material and missing information, then identify useful additions and unresolved evidence needs.

Act on the questions the saved comments already support before you fetch more pages for another condition or viewpoint. Root-comment pages and reply pages are separate requests; budget each with current [pricing](https://beatapi.io/pricing).

[Post and creator identity](/faq/kuaishou-identifiers) · [Search and selection guide](/guides/kuaishou-filtered-search)