ToolRouter exposes connected-account operations for supported X and LinkedIn publishing. The agent should discover the exact operation, verify the upstream account and publish the content you authorised. Research access to a social platform does not imply publishing support.
What is supported in the current catalog?
| Tool | Operation | Purpose |
|---|---|---|
linkedin-post | post_text | Publish an authorised text post |
linkedin-post | post_link | Publish an authorised link post |
linkedin-post | post_image | Publish an authorised image post |
x-manager | post_tweet | Publish an authorised X text post |
x-manager | post_image_tweet | Publish an authorised X image post |
These operation names were present in the live catalog on 3 October 2026. Your client profile, connected account and provider permissions determine actual access. Inspect the live schema each time rather than copying stale input field names.
A publishing workflow
- Specify the platform, exact account, content and whether you want a draft or publication.
- Discover the appropriate posting operation and inspect its inputs, price and account requirements.
- Verify the connected account identity before executing.
- Review the final text, link and media. Use the authorisation already given for that concrete post; ask if the request only covers drafting.
- Execute once, then inspect the returned provider result or status before retrying.
- Return the post ID or URL when supplied, and state any provider error or unresolved status.
Example discovery input:
{
"query": "publish an authorised text post to my connected LinkedIn account"
}Example task:
Prepare a LinkedIn text post from the announcement I provide. Use ToolRouter to discover the operation and verify the account, then show the final post and any price for my approval before publishing. Do not add claims absent from the announcement.
Drafting and posting are separate permissions
A request to write a post does not authorise publication. An account connection is also not permission to message people, delete a post, follow accounts or change settings. Follow the actual user request and the discovered operation scope.
If the user has already approved the exact content and destination, complete the authorised action without asking for the same approval again.
Media and source checks
An image operation may need a supported upload or publicly reachable file URL; a local path is not enough. Follow files and media, inspect accepted media fields and retain the final approved asset.
A scrape or search operation for Instagram, TikTok or YouTube is a reading operation. This guide does not establish publishing support for those platforms, bulk scheduling or social analytics.
Retries, costs and proof
Inspect the operation's price and credits before paid work. If a write times out, read status or the upstream provider before retrying. A repeated request after an uncertain response can create a duplicate post.
A queued action is unfinished. A provider success response establishes what the provider accepted; use a returned post link or readback to confirm the published result where available. Keep provider errors visible and do not report a draft as a live post.
Recurring content
An MCP connection alone does not create a publishing scheduler. A recurring runtime needs a defined cadence, account, content source, approval rule and budget. Do not infer a scheduling feature from the presence of a post operation.