MCP tools and tasks
Explore available tools and workspace selection rules.
Ask your AI client for a task and it calls the corresponding tool. Start with “Use Posteady to show my connected accounts and what each supports.”
Available tools
| Tool | Task |
|---|---|
list_workspaces | List eligible workspaces |
list_accounts | Read connections and capabilities |
list_posts | Read posts and synchronized metrics from the last 90 days |
list_media | List media in the selected workspace |
create_media_upload | Reserve an upload URL |
confirm_media_upload | Confirm uploaded bytes |
publish_post | Publish text or enqueue an asynchronous job |
get_publish_status | Track an asynchronous job by jobId |
repost_post | Reshare a supported platform post |
schedule_post | Schedule a future post |
list_scheduled_posts | List scheduled posts |
cancel_scheduled_post | Cancel a pending schedule |
Workspace selection
list_accounts, list_posts, and list_scheduled_posts read across eligible accessible workspaces when workspaceId is omitted. Pass an ID from list_workspaces to narrow the result.
publish_post and schedule_post derive the workspace from accountIds; repost_post uses accountId; get_publish_status uses jobId; and cancel_scheduled_post uses scheduledPostId and platform. Optional workspaceId asserts the expected workspace; it does not move the resource.
Media tools use an explicit workspaceId, or the default workspace when omitted. Match the upload workspace to the publishing account.
Publishing and media
Specify both target and content, such as “Publish this text to my Threads account.” Threads, X, and LinkedIn use posts. TikTok uses posts + video; Instagram, YouTube, and Facebook use their respective instagram, youtube, and facebook objects. The platform guide’s input also applies to these MCP tools.
For X, publish_post and schedule_post automatically remove links from posts[0], including http://, https://, www., and bare domains with paths, query strings, or fragments. Reply links (posts[1] onward) and other platforms' text stay unchanged. X length limits are checked after removal; an empty first post rejects the entire request with VALIDATION_ERROR before publishing or saving any schedule. Put links in replies to share them. See X examples and scheduling scope.
New files follow create_media_upload → PUT bytes to the returned URL → confirm_media_upload. Do not send base64 file data to the tool. If your client cannot PUT a local file, upload through Posteady first and select it with list_media.
For asynchronous publishing, pass the returned jobId to get_publish_status. At unknown, inspect the target platform; do not automatically create another publishing request.
Scheduling and reporting
Specify a timezone, such as “Schedule this for 9 a.m. tomorrow in Asia/Seoul.” schedule_post accepts a future scheduledAt and optional timezone. Use scheduledPostId for cancellation and jobId for publishing status.
Try “Show my recent posts with the highest views.” list_posts returns at most 100 posts from the last 90 days, without date-range or pagination parameters. A client can filter returned posts further, but must not treat that subset as a complete report including posts that were not returned.
Platform examples · Upload workflow · Schedule and cancel · Metric semantics