Post a tweet on X (Twitter) from an AI agent, no API key

The tweet body text (≤280 chars, as X weighs it). Any @handle in the text is validated against a real, non-suspended X account before anything is posted — the run throws naming the bad handle if one doesn't resolve. Unless dry_run is set, every call posts immediately and irreversibly in public, with no preview or confirmation step inside the script, so show the exact text and any media to the user and get their explicit approval for this specific content before running — approval from an earlier or unrelated message does not carry over.

When true, everything runs — the media is attached and staged and the text is typed — and then the run stops immediately before the Post click. Nothing is published: tweet_id and url come back null and dry_run is true. Use it to verify text and media are accepted without spending a real, irreversible public tweet.

Optional link to one image (JPEG, PNG, GIF, WebP) or video (MP4) to attach. The browser fetches it, so any host it can reach works, including a file served from the machine running the browser (python3 -m http.server 8765 --bind 127.0.0.1 → http://127.0.0.1:8765/pic.jpg). No size ceiling. The link must point at the file itself — a page about the file is refused before anything is published.

One image or video to attach, bound through the platform's own file channel and handed straight to the composer's file input. Carries the bytes outside the argument payload, so unlike media_base64 it is not limited by the request size, and it works on every device. Pass at most one of attachment / media_url / media_base64.

Optional image or video as base64 bytes, as an alternative to media_url. A data: prefix, line wrapping and base64url characters are all accepted. Suitable only for small files: arguments arriving over MCP are capped around 96KB of base64 by the transport itself. Prefer the `attachment` input, which has no such cap, or media_url. Generate it with a command (base64 -i pic.jpg | tr -d '\n') rather than typing it — hand-copied base64 corrupts easily.

Optional filename to present the attachment under (e.g. chart.png). Defaults to the name in media_url, or 'media' plus the extension matching the detected file type. Not used with the `attachment` input, which carries its own name.

Permalink of the new tweet. Null on a dry run, where nothing was published.

Null on a dry run, where nothing was published.

Number of media attachments on the posted tweet (0 if text-only), read back from X's own response to the publish. On a dry run this is what was staged, not what was published.

handle of the logged-in account that performed the action, read from the account switcher UI (not assumed from input).

true if a post with this exact text was already found on the account's own timeline before attempting to publish (duplicate-avoidance check); when true, publishing is skipped and tweet_id/url are null.

true if the script navigated to the new tweet's URL after publishing and confirmed the article is actually present. Always false on a dry run.

True when this run stopped before the Post click and published nothing. The media was still attached and the text still typed — only the final publish was skipped.

The attachment's detected type (e.g. image/jpeg, video/mp4), or null on a text-only post.

Size in bytes of the attached file as the browser decoded it, so a truncated payload is visible in the result. Null when no media was attached, or when it came from media_path or the attachment input.