Media

Video Audio Extract Enhanced

Extract audio from video files with advanced options - multiple formats, quality settings, and audio enhancement

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/video-audio-extract-enhanced' \
  -F 'file=@/path/to/videoFile.ext'

# 2) Call the tool with the returned filePath values
curl -X POST 'https://api.elysiatools.com/en/api/tools/video-audio-extract-enhanced' \
  -F 'videoFile=/path/to/file.ext' \
  -F 'audioFormat=mp3' \
  -F 'bitrate=192' \
  -F 'sampleRate=44100' \
  -F 'channels=original' \
  -F 'normalize=false' \
  -F 'startTime=00:00:00 or 30 (seconds)' \
  -F 'duration=00:05:00 or 300 (seconds)'

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/video-audio-extract-enhanced

Parameters

Name	Type	Required	Description
videoFile	fileupload required	Yes	—
audioFormat	select	No	Audio format for extracted audio
bitrate	select	No	Audio bitrate (lossless formats ignore this)
sampleRate	select	No	Audio sample rate
channels	select	No	Audio channel configuration
normalize	checkbox	No	Apply EBU R128 loudness normalization
startTime	text	No	Start time for extraction (HH:MM:SS or seconds, empty = from beginning)
duration	text	No	Duration to extract (HH:MM:SS or seconds, empty = to end)

File-type parameters must be uploaded first via POST /upload/video-audio-extract-enhanced, 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-video-audio-extract-enhanced": {
      "name": "video-audio-extract-enhanced",
      "description": "Extract audio from video files with advanced options - multiple formats, quality settings, and audio enhancement",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=video-audio-extract-enhanced",
      "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": "video-audio-extract-enhanced",
    "arguments": {
  "videoFile": "https://example.com/file.ext",
  "audioFormat": "mp3",
  "bitrate": "192",
  "sampleRate": "44100",
  "channels": "original",
  "normalize": false,
  "startTime": "00:00:00 or 30 (seconds)",
  "duration": "00:05:00 or 300 (seconds)"
}
  }
}

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]