List Lemmy post comments
lemmy_post_comments_listList comments on a Lemmy post or replies to a specific comment by providing the instance; paginate with a cursor for larger threads.
Instructions
List comments on one Lemmy post, or the replies to one comment. Requires instance. Returns a list (use cursor when paginated).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"instance": "<instance>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "lemmy_post_comments_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, 1 to 100. Default: 1. An instance refuses pages past 100. Lemmy pages by number over a live order, so new or re-ranked items can shift a row onto the next page. Remove repeats by `id`. | |
| sort | No | Order. `Controversial` is refused by 0.18 instances. | |
| limit | No | Rows per page, 1 to 50. Default: 10. | |
| cursor | No | Pass `page.nextCursor` from the previous response to get the next page. It only works with the same filters; do not send it with `page`. | |
| postId | No | Post id on the chosen instance, e.g. `53910627`. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| instance | Yes | Required. The Lemmy instance, e.g. `lemmy.world`. A URL on the instance is also accepted. Ids and counts belong to this instance. | |
| parentId | No | List this comment and its replies instead of the whole post. Walk a deeper branch by passing one of its reply ids here. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess. | |
| conversation_id | No | Echo the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it. |