List the audio files on this R3 account
r3_audio_listList the audio files this R3 account owns, with the URL to use for each one. That URL is exactly what R3ComponentAudio.url takes, so this is how you find a sound the account already has — a footstep, a drum hit, a music bed — and then point an Audio component at it with r3_component_set.
Search by name rather than paging: search: "kick" is matched against every audio file on the account by the server, not against the page you happen to be holding.
You cannot upload an audio file from here — a tool argument is JSON, this server cannot read your disk, and audio is megabytes. A person uploads those in the R3 app. r3_sound_create makes a new sound effect or seamless loop from a recipe (rendered by R3, listed here afterwards); R3's music components (Transport, Beat, Pattern, DrumGrid) synthesise music that stays editable and in tempo.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "r3_audio_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many to return (default 25, max 100). | |
| cursor | No | Continue a previous listing: pass the nextCursor it returned, unchanged. Omit for the first page. | |
| search | No | Match this text against the file names, on the server. Omit for everything. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | Yes | ||
| answer | Yes | This answer in words: what was done, what R3 measured, decided or refused, and what to do next. The same text as the result's text block. Read it: the fields beside it are the data, this is the guidance. | |
| audios | Yes | ||
| search | Yes | ||
| hasMore | Yes | ||
| nextCursor | Yes |