Media

Podcast Chapter Marker Builder

Build every podcast chapter format from one timecoded list: Podcasting 2.0 JSON + RSS tag, ID3v2.4 CHAP+CTOC burned into an MP3, Vorbis comments, mp4chaps, YouTube timestamps and SRT, with a per-player support matrix.

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 'http://127.0.0.1:3003/api/upload/presign/podcast-chapter-marker-builder' \
  -H 'Content-Type: application/json' \
  -d '{"filename":"mp3File.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 'http://127.0.0.1:3003/en/api/tools/podcast-chapter-marker-builder' \
  -F 'chapterList=0:00 Cold open
1:13 Interview: scaling Kafka consumers
6:58 Listener questions
18:40 Tooling corner
41:05 Corrections
52:30 Outro' \
  -F 'mp3File=uploads/2026/01/01/your-tool-1700000000000-abc123.ext' \
  -F 'podcastName=Ship It!' \
  -F 'episodeTitle=Ep. 204 — Scaling Kafka Consumers' \
  -F 'jsonUrl=shipit.example/ep204/chapters.json' \
  -F 'chapterImage='

API reference

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

Endpoint

HTTP

POST http://127.0.0.1:3003/en/api/tools/podcast-chapter-marker-builder

Parameters

Name	Type	Required	Description
chapterList	textarea	Yes	—
mp3File	fileupload required	No	—
podcastName	text	No	—
episodeTitle	text	No	—
jsonUrl	text	No	—
chapterImage	text	No	—

File-type parameters must be uploaded first via POST /upload/podcast-chapter-marker-builder, 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-podcast-chapter-marker-builder": {
      "name": "podcast-chapter-marker-builder",
      "description": "Build every podcast chapter format from one timecoded list: Podcasting 2.0 JSON + RSS tag, ID3v2.4 CHAP+CTOC burned into an MP3, Vorbis comments, mp4chaps, YouTube timestamps and SRT, with a per-player support matrix.",
      "baseUrl": "http://127.0.0.1:3003/mcp/sse?toolId=podcast-chapter-marker-builder",
      "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": "podcast-chapter-marker-builder",
    "arguments": {
  "chapterList": "0:00 Cold open\n1:13 Interview: scaling Kafka consumers\n6:58 Listener questions\n18:40 Tooling corner\n41:05 Corrections\n52:30 Outro",
  "mp3File": "https://example.com/file.ext",
  "podcastName": "Ship It!",
  "episodeTitle": "Ep. 204 — Scaling Kafka Consumers",
  "jsonUrl": "shipit.example/ep204/chapters.json",
  "chapterImage": ""
}
  }
}

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]