---
description: Post a tweet to X
---

Post the text "$ARGUMENTS" to X.

## Workflow

1. If the text is empty, ask the user what to tweet.
2. Resolve the connected X username. Ask the user if it is unknown.
3. Show the exact text, account, endpoint, and usage estimate.
4. Wait for explicit user confirmation.
5. After confirmation, call `POST /api/v1/x/tweets` with the `execute` MCP tool and the body
   `{ "account": "<confirmed account>", "text": "<the tweet text>" }`.
   Hosted MCP injects a unique `Idempotency-Key`.
6. Accept HTTP 200 or 202. Wait for `pollAfterMs`, then poll `statusUrl`.
   Stop when `terminal` is true.
7. Show the confirmed tweet ID and `https://x.com/i/status/{tweetId}`.

The API requires `account` and `Idempotency-Key` on every post request. Direct
REST callers must supply the header. Hosted MCP supplies it automatically.
Start a new attempt only when `safeToRetry` is true.