Search Polymarket
polymarket_searchSearch Polymarket events, tags, and profiles by keyword to locate prediction markets, related tags, or user profiles; paginate results as needed.
Instructions
Search Polymarket events, tags and profiles by keyword. Requires query. Returns a list (use page 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": {
"query": "<query>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "polymarket_search"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, 1–100. Default: 1. Polymarket can stop a deep page early and report `hasMore: false`. | |
| query | Yes | Required. Search text. The index is English: other scripts return nothing. | |
| types | No | What to search, comma separated: `events`, `tags`, `profiles`. Default: `events,tags`. | |
| locale | No | Translate titles and market questions into this language. Descriptions stay in English. | |
| context | Yes | Describe the user's underlying goal in one sentence, not the tool you are calling. | |
| 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. | |
| limitPerType | No | Items per page, 1–50. Default: 10. | |
| 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. |