Media

Audio Chorus

Apply a chorus effect

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Upload each file first → returns { filePath }
curl -X POST 'https://api.elysiatools.com/upload/audio-chorus' \
  -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-chorus' \
  -F 'audioFile=/path/to/file.ext' \
  -F 'voices=[
  {
    "inGain": 0.5,
    "outGain": 0.9,
    "delay": 40,
    "decay": 0.4,
    "speed": 0.25,
    "depth": 2
  },
  {
    "inGain": 0.5,
    "outGain": 0.9,
    "delay": 50,
    "decay": 0.4,
    "speed": 0.3,
    "depth": 2
  }
]' \
  -F 'outputFormat=mp3'

API reference

Send a POST request with your inputs as JSON. File parameters require a separate upload first.

Endpoint

HTTP

POST https://api.elysiatools.com/en/api/tools/audio-chorus

Parameters

Name	Type	Required	Description
audioFile	fileupload required	Yes	—
voices	textarea	No	—
outputFormat	select	No	—

File-type parameters must be uploaded first via POST /upload/audio-chorus, then the returned filePath is passed to the corresponding file field.

Response format

File result

JSON

{
  "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)"
}

MCP integration

Add this tool to your Model Context Protocol server so AI agents can list and call it.

Server configuration

Add this block to your MCP client configuration:

mcp.json

{
  "mcpServers": {
    "elysiatools-audio-chorus": {
      "name": "audio-chorus",
      "description": "Apply a chorus effect",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=audio-chorus",
      "command": "",
      "args": [],
      "env": {},
      "isActive": true,
      "type": "sse"
    }
  }
}

List available tools

After connecting to the SSE endpoint, list the exposed tools:

tools/list

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Call this tool

Invoke the tool by its id, passing arguments built from its parameters:

tools/call

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "audio-chorus",
    "arguments": {
  "audioFile": "https://example.com/file.ext",
  "voices": "[\n  {\n    \"inGain\": 0.5,\n    \"outGain\": 0.9,\n    \"delay\": 40,\n    \"decay\": 0.4,\n    \"speed\": 0.25,\n    \"depth\": 2\n  },\n  {\n    \"inGain\": 0.5,\n    \"outGain\": 0.9,\n    \"delay\": 50,\n    \"decay\": 0.4,\n    \"speed\": 0.3,\n    \"depth\": 2\n  }\n]",
  "outputFormat": "mp3"
}
  }
}

Chain multiple tools in one session with a comma-separated toolId list, e.g. /mcp/sse?toolId=png-to-webp,jpg-to-webp,gif-to-webp (max 20).

File parameters accept a public file URL only (https://…). Local paths, data: URIs, and Base64 strings are not supported.

Questions or issues? Contact [email protected]