Media

Audio Filler Word Removal Map

Combine a timestamped transcript with the audio to mark filler words (um, uh, 嗯, 那个…) and optionally mute or remove them.

file· File resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL

# 1) Request a presigned URL → returns { uploadUrl, storageKey }
curl -X POST 'https://api.elysiatools.com/api/upload/presign/audio-filler-word-removal-map' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"audioFile.ext","contentType":"application/octet-stream","size":12345}'

# 2) PUT the file bytes directly to the presigned uploadUrl
curl -X PUT '<presigned uploadUrl>' \
  --data-binary @/path/to/file.ext

# 3) Call the tool, passing the returned storageKey for each file field
curl -X POST 'https://api.elysiatools.com/en/api/tools/audio-filler-word-removal-map' \
  -F 'audioFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'transcript=Paste SRT, VTT, or "0:05 hello world" lines…' \
  -F 'fillerLanguage=en' \
  -F 'customFillers=um, uh, hmm' \
  -F 'outputMode=map' \
  -F 'padAroundCut=0.05' \
  -F 'outputFormat=wav'

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-filler-word-removal-map

Parameters

Name	Type	Required	Description
audioFile	fileupload required	Yes	—
transcript	textarea	Yes	—
fillerLanguage	select	No	—
customFillers	text	No	—
outputMode	select	No	—
padAroundCut	number	No	—
outputFormat	select	No	—

File-type parameters must be uploaded first via POST /upload/audio-filler-word-removal-map, 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-filler-word-removal-map": {
      "name": "audio-filler-word-removal-map",
      "description": "Combine a timestamped transcript with the audio to mark filler words (um, uh, 嗯, 那个…) and optionally mute or remove them.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=audio-filler-word-removal-map",
      "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-filler-word-removal-map",
    "arguments": {
  "audioFile": "https://example.com/file.ext",
  "transcript": "Paste SRT, VTT, or \"0:05 hello world\" lines…",
  "fillerLanguage": "en",
  "customFillers": "um, uh, hmm",
  "outputMode": "map",
  "padAroundCut": 0.05,
  "outputFormat": "wav"
}
  }
}

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]