Text Processing

Divisor de hilos de Twitter / X

Pega un texto largo y divídelo en un hilo numerado de X que respeta el límite de 280 caracteres. Divide por límites de palabra/oración/párrafo, añade numeración 1/N, pondera correctamente CJK y caracteres de ancho completo, cuenta las URLs como 23 caracteres y muestra una tarjeta de estilo X con medidor de caracteres.

html· Resultado HTMLAbrir herramienta

Inicio rápido

Llama a esta herramienta desde tu código en tres lenguajes.

cURL

curl -X POST 'https://api.elysiatools.com/es/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}'

Explorar herramientas

Text Processing

Divisor de hilos de Twitter / X

html· Resultado HTMLAbrir herramienta

Inicio rápido

Llama a esta herramienta desde tu código en tres lenguajes.

cURL

curl -X POST 'https://api.elysiatools.com/es/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}'

Nombre	Tipo	Obligatorio	Descripción
text	textarea	Sí	The text you want to split into an X thread.
limit	number	Sí	Character budget per tweet. 280 is the standard X limit (CJK and URLs are weighted per X rules).
mode	select	No	—
numbering	select	No	—
separator	text	No	Text placed between content and the numbering tag (e.g. — or a newline).
keepBreaks	checkbox	No	—
reserveUrl	checkbox	No	When on, URLs count as 23 characters (X behaviour). When off, URLs count by their raw length.

{ "mcpServers": { "elysiatools-twitter-thread-splitter": { "name": "twitter-thread-splitter", "description": "Pega un texto largo y divídelo en un hilo numerado de X que respeta el límite de 280 caracteres. Divide por límites de palabra/oración/párrafo, añade numeración 1/N, pondera correctamente CJK y caracteres de ancho completo, cuenta las URLs como 23 caracteres y muestra una tarjeta de estilo X con medidor de caracteres.", "baseUrl": "https://api.elysiatools.com/mcp/sse?toolId=twitter-thread-splitter", "command": "", "args": [], "env": {}, "isActive": true, "type": "sse" } } }

{ "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 } } }

Divisor de hilos de Twitter / X

Inicio rápido

Divisor de hilos de Twitter / X

Inicio rápido

Referencia de la API

Endpoint

Parámetros

Formato de respuesta

Integración MCP

Configuración del servidor

Listar herramientas disponibles

Llamar a esta herramienta