List Polymarket event comments
polymarket_event_comments_listFetch comments and replies for a Polymarket event, sorted newest or oldest, with no depth limit and cursor pagination; requires the event ID.
Instructions
List the comments and replies on a Polymarket event, newest or oldest first, with no depth limit. Requires eventId. 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": {
"eventId": "<eventId>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "polymarket_event_comments_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| sort | No | Order of top-level comments by time. Default: `newest`. Polymarket can sort by likes only on a route that stops after 250 rows, so it is not offered here. | |
| limit | No | Top-level comments per page, 1–100. Default: 40. Replies come with their parent and do not count towards the limit. | |
| cursor | No | Pass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| eventId | Yes | Required. Event id (digits). Slugs are not accepted 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. | |
| holdersOnly | No | `true` keeps comments by people who hold a position. | |
| 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. |