Media
Slice audio by beats and reorder or loop
Call this tool from your code in three languages.
# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/audio-beat-slicer' \
-F 'file=@/path/to/audioFile.ext'
# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/audio-beat-slicer' \
-F 'audioFile=/path/to/file.ext' \
-F 'bpm=0' \
-F 'beatsPerSlice=1' \
-F 'pattern=original' \
-F 'loopCount=2' \
-F 'outputFormat=mp3'Send a POST request with your inputs as JSON. File parameters require a separate upload first.
POST https://api.elysiatools.com/en/api/tools/audio-beat-slicer| Name | Type | Required | Description |
|---|---|---|---|
| audioFile | fileupload required | Yes | — |
| bpm | number | No | — |
| beatsPerSlice | number | No | — |
| pattern | select | No | — |
| loopCount | number | No | — |
Add this tool to your Model Context Protocol server so AI agents can list and call it.
Add this block to your MCP client configuration:
{
"mcpServers": {
"elysiatools-audio-beat-slicer": {
"name": "audio-beat-slicer",
"description": "Slice audio by beats and reorder or loop",
"baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=audio-beat-slicer",
"command": "",
"args": [],
"env": {},
"isActive": true,
"type": "sse"
}
}
}After connecting to the SSE endpoint, list the exposed tools:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list"
}Invoke the tool by its id, passing arguments built from its parameters:
{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/call",
"params": {
"name": "audio-beat-slicer",
"arguments": {
"audioFile": "https://example.com/file.ext",
"bpm": 0,
"beatsPerSlice": 1,
"pattern": "original",
"loopCount": 2,
"outputFormat": "mp3"
}
}
}| outputFormat | select | No | — |
File result
{
"filePath": "/public/processing/randomid.ext",
"fileName": "output.ext",
"contentType": "application/octet-stream",
"size": 1024,
"metadata": {
"key": "value"
},
"error": "Error message (optional)",
"message": "Notification message (optional)"
}Questions or issues? Contact [email protected]