Twitter / X
Twitter (X) API-based operations: publish tweets/threads/carousels, fetch metrics, fetch mentions, get profile, and reply via API. For browser-based actions (browsing the timeline, engaging in the browser, scraping the UI) use the `browse` skill instead.
twitter 5 BST per callWhat it does
Twitter/X via the official API. Publish text, threads, and replies; pull metrics and profile data. Browser-mediated actions are gone — the generic `browse` skill handles anything that needs server-side Steel CDP.
When to use it
Brandstaq automatically picks Twitter / X when you say things like:
- “Tweet this thread now”
- “Reply to the top mention from this morning”
- “Get profile stats for our X account”
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| limit | integer | No | — |
| posts | array | No | — |
| query | string | No | Search query (max 512 chars). |
| action | string | Yes | Twitter operation to perform. Each value maps to a connector method; mismatched action/params return UNKNOWN_ACTION. |
| caption | string | No | — |
| content | string | No | — |
| post_id | string | No | — |
| parent_id | string | No | — |
| media_path | string | No | Required for media tweets (image/video). For text-only tweets, use publish_text instead. |
| media_type | string | No | — |
| max_results | integer | No | — |
| media_paths | array | No | — |
| since_cursor | string | No | — |
When the agent reaches for it
When you mention Twitter or X explicitly — tweet a thread, reply to a mention, get profile stats — the agent reaches for this. Anything that needs raw browser automation falls through to the generic browse skill instead.