Media

Audio Caption Sync Checker

Compare SRT or WebVTT cue timing with likely speech activity and flag timing drift.

json· JSON 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-caption-sync-checker' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"audioFile.ext","contentType":"application/octet-stream","size":12345}'
curl -X POST 'https://api.elysiatools.com/api/upload/presign/audio-caption-sync-checker' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"captionFile.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-caption-sync-checker' \
  -F 'audioFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'captionFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'captionFormat=auto' \
  -F 'toleranceSeconds=0.25'

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-caption-sync-checker

Parameters

Name	Type	Required	Description
audioFile	fileupload required	Yes	—
captionFile	fileupload required	Yes	—
captionFormat	select	No	—
toleranceSeconds	number	No	—

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

Response format

JSON result

JSON

{
  "key": {...},
  "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-caption-sync-checker": {
      "name": "audio-caption-sync-checker",
      "description": "Compare SRT or WebVTT cue timing with likely speech activity and flag timing drift.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=audio-caption-sync-checker",
      "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-caption-sync-checker",
    "arguments": {
  "audioFile": "https://example.com/file.ext",
  "captionFile": "https://example.com/file.ext",
  "captionFormat": "auto",
  "toleranceSeconds": 0.25
}
  }
}

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]