List Deezer events
deezer_events_listSearch upcoming Deezer concerts and festivals by place or act, with optional event-type filters and pagination, to find relevant live events.
Instructions
Search upcoming Deezer concerts and festivals by place or act. Optional inputs: query, type, limit and cursor. 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": {
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "deezer_events_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Only this kind of event. Default: both. | |
| limit | No | Items per page, 1 to 100. Default: 50. | |
| query | No | A place or an act, for example `London` or `Metallica`. Without it the endpoint lists events Deezer still marks as pending in the United Kingdom. | |
| cursor | No | Pass `page.nextCursor` from the previous response to get the next page. Keep the other parameters the same. | |
| 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. | |
| 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. |