List Deezer playlist tracks
deezer_playlist_tracks_listLists tracks in a Deezer playlist in order with each track's date added. Use the playlist ID and paginate with a cursor for up to 1,000 tracks per page.
Instructions
List a Deezer playlist's tracks in order with the date each was added, up to 1,000 per page. Requires playlistId. 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": {
"playlistId": "<playlistId>",
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "deezer_playlist_tracks_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Items per page, 1 to 1000. Default: 100. | |
| 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. | |
| playlistId | Yes | Required. Deezer playlist id, for example `908622995`. | |
| 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. |