Text Processing

Divisor de thread do Twitter / X

Cole um texto longo e divida-o em um thread X numerado que respeita o limite de 280 caracteres. Divide em fronteiras de palavra/frase/parágrafo, adiciona numeração 1/N, pondera corretamente CJK e caracteres de largura total, conta URLs como 23 caracteres e mostra um cartão estilo X com medidor.

html· Resultado HTMLAbrir ferramenta

Início rápido

Chame esta ferramenta a partir do seu código em três idiomas.

cURL

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

Text Processing

Divisor de thread do Twitter / X

html· Resultado HTMLAbrir ferramenta

Início rápido

Chame esta ferramenta a partir do seu código em três idiomas.

cURL

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

Nome	Tipo	Obrigatório	Descrição
text	textarea	Sim	The text you want to split into an X thread.
limit	number	Sim	Character budget per tweet. 280 is the standard X limit (CJK and URLs are weighted per X rules).
mode	select	Não	—
numbering	select	Não	—
separator	text	Não	Text placed between content and the numbering tag (e.g. — or a newline).
keepBreaks	checkbox	Não	—
reserveUrl	checkbox	Não	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": "Cole um texto longo e divida-o em um thread X numerado que respeita o limite de 280 caracteres. Divide em fronteiras de palavra/frase/parágrafo, adiciona numeração 1/N, pondera corretamente CJK e caracteres de largura total, conta URLs como 23 caracteres e mostra um cartão estilo X com medidor.", "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 thread do Twitter / X

Início rápido

Divisor de thread do Twitter / X

Início rápido

Referência da API

Endpoint

Parâmetros

Formato de resposta

Integração MCP

Configuração do servidor

Listar ferramentas disponíveis

Chamar esta ferramenta