Elysia Tools Docs
EN
Language
ZHESPTRUFRDEEN
Back to site
Browse tools

Media

Subtitle Platform Spec Checker

Validate subtitles against delivery specs: Netflix Timed Text (20/17 CPS reading speed, 42 characters per line, two lines, 5/6-second minimum and 7-second maximum durations, 2-frame gaps), BBC television guidelines (37 characters per line, 160-180 wpm, 1.5-second pause gaps) and YouTube caption rules (plain UTF-8, markup not recognized) — with a per-cue findings report.

html· HTML 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/subtitle-platform-spec-checker' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"subtitleFile.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/subtitle-platform-spec-checker' \
  -F 'subtitleFile=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'profile=netflix-adult' \
  -F 'fps=24'

© 2026 Elysia Tools. Developer documentation.

Back to siteBrowse tools

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/subtitle-platform-spec-checker

Parameters

NameTypeRequiredDescription
subtitleFilefileupload requiredYes—
profileselectNo—
fpsnumberNo—
File-type parameters must be uploaded first via POST /upload/subtitle-platform-spec-checker, then the returned filePath is passed to the corresponding file field.

Response format

HTML result

JSON
{
  "result": "<div>Processed HTML content</div>",
  "error": "Error message (optional)",
  "message": "Notification message (optional)",
  "metadata": {
    "key": "value"
  }
}

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-subtitle-platform-spec-checker": {
      "name": "subtitle-platform-spec-checker",
      "description": "Validate subtitles against delivery specs: Netflix Timed Text (20/17 CPS reading speed, 42 characters per line, two lines, 5/6-second minimum and 7-second maximum durations, 2-frame gaps), BBC television guidelines (37 characters per line, 160-180 wpm, 1.5-second pause gaps) and YouTube caption rules (plain UTF-8, markup not recognized) — with a per-cue findings report.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=subtitle-platform-spec-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": "subtitle-platform-spec-checker",
    "arguments": {
  "subtitleFile": "https://example.com/file.ext",
  "profile": "netflix-adult",
  "fps": 24
}
  }
}
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]

Browse tools
Open tool