Elysia Tools Docs
EN
Language
ZHESPTRUFRDEEN
Back to site
Browse tools

Text Processing

Twitter / X Thread Splitter

Paste a long text and split it into a numbered X thread that respects the 280-character limit. Splits on word/sentence/paragraph boundaries, auto-adds 1/N numbering, weighs CJK and full-width characters correctly, counts URLs as 23 characters, and shows a live X-style preview card for each tweet with a character meter.

html· HTML resultOpen tool

Quick start

Call this tool from your code in three languages.

cURL
curl -X POST 'https://api.elysiatools.com/en/api/tools/twitter-thread-splitter' \
  -H 'Content-Type: application/json' \
  -d '{"text":"Designing for latency is harder than designing for throughput. Throughput rewards batching and parallelism. Latency punishes them, because every extra hop adds queuing delay. The fastest request is the one you never make. Cache aggressively, but measure the cache hit ratio — a 50% hit rate barely helps P99. Finally, budget for failure: retries and timeouts are themselves latency sources, and they compound under load.","limit":280,"mode":"sentence","numbering":"slash","separator":"—","keepBreaks":true,"reserveUrl":true}'

© 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/twitter-thread-splitter

Parameters

NameTypeRequiredDescription
texttextareaYesThe text you want to split into an X thread.
limitnumberYesCharacter budget per tweet. 280 is the standard X limit (CJK and URLs are weighted per X rules).
modeselectNo—
numberingselectNo—
separatortextNoText placed between content and the numbering tag (e.g. — or a newline).
keepBreakscheckboxNo—
reserveUrlcheckboxNoWhen on, URLs count as 23 characters (X behaviour). When off, URLs count by their raw length.

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-twitter-thread-splitter": {
      "name": "twitter-thread-splitter",
      "description": "Paste a long text and split it into a numbered X thread that respects the 280-character limit. Splits on word/sentence/paragraph boundaries, auto-adds 1/N numbering, weighs CJK and full-width characters correctly, counts URLs as 23 characters, and shows a live X-style preview card for each tweet with a character meter.",
      "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=twitter-thread-splitter",
      "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": "twitter-thread-splitter",
    "arguments": {
  "text": "Designing for latency is harder than designing for throughput. Throughput rewards batching and parallelism. Latency punishes them, because every extra hop adds queuing delay. The fastest request is the one you never make. Cache aggressively, but measure the cache hit ratio — a 50% hit rate barely helps P99. Finally, budget for failure: retries and timeouts are themselves latency sources, and they compound under load.",
  "limit": 280,
  "mode": "sentence",
  "numbering": "slash",
  "separator": "—",
  "keepBreaks": true,
  "reserveUrl": true
}
  }
}
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).

Questions or issues? Contact [email protected]

Browse tools
Open tool