Posteady
Posteady Docs
User guideDeveloper guidesAPI referenceMCP
MCPGetting started

MCP tools and tasks

Explore available tools and workspace selection rules.

Tell your AI client what you want to do, and it calls the right tool. Start with “Use Posteady to show my connected accounts and what each supports.”

Available tools

ToolTask
list_workspacesList eligible workspaces
list_accountsRead connections and capabilities
list_postsRead posts and synchronized metrics for a period (the last 90 days by default)
get_account_analyticsRead follower changes and post performance per account for a period
list_mediaList media in the selected workspace
create_media_uploadReserve an upload URL
confirm_media_uploadConfirm uploaded bytes
import_media_from_urlDownload an image or video from a link to the media library
publish_postPublish text or enqueue an asynchronous job
get_publish_statusTrack an asynchronous job by jobId
repost_postReshare a supported platform post
schedule_postSchedule a future post
list_scheduled_postsList scheduled posts
cancel_scheduled_postCancel a pending schedule
replace_scheduled_postReplace a pending schedule with new content, media, or time
create_carouselSubmit a topic, text, or link to generate a carousel
get_carouselCheck generation status and rendered slide images by carouselId
list_carousel_optionsList templates and brands for carousels
create_channel_textsWrite a post for each account from one source, in its persona voice
list_commentsRead comments on your posts with comment inbox statuses
reply_to_commentReply to a comment as the account that received it
hide_commentHide a comment or show it again
delete_commentDelete a comment
save_chat_imagesChatGPT only: save images attached to or generated in the conversation to the media library

Workspace selection

list_accounts, list_posts, get_account_analytics, list_comments, and list_scheduled_posts read across all eligible workspaces you can access when workspaceId is omitted. Pass an ID from list_workspaces to narrow the result.

publish_post, schedule_post, and replace_scheduled_post derive the workspace from accountIds; repost_post and the comment tools that act on a comment use accountId; get_publish_status uses jobId; and cancel_scheduled_post uses scheduledPostId and platform. An optional workspaceId only checks that the target is in that workspace; it does not move the resource.

Media tools, carousel tools, and create_channel_texts use an explicit workspaceId, or the default workspace when omitted. Upload media to the same workspace as the account you'll publish from.

Publishing and media

Specify both the target and the content, such as “Publish this text to my Threads account.” Threads, X, and LinkedIn use posts. TikTok uses posts + video or posts + tiktokPhoto; Instagram, YouTube, and Facebook use their respective instagram, youtube, and facebook objects. The platform guide’s input also applies to these MCP tools.

Threads, X, and LinkedIn posts can carry images from the media library: add their IDs as mediaIds to publish_post or schedule_post. The images go on the first post; replies stay text. Threads takes 1–20 (2 or more become a carousel), X takes 1–4 of up to 5 MiB each, and LinkedIn takes 1–20. With several platforms, the smallest limit applies. To put images on replies in a Threads or X thread, use mediaIdsByPost instead, with one list of IDs per post. Threads posts can also carry MP4 and MOV videos of up to 5 minutes, alone or mixed with images in a carousel, and a LinkedIn post can carry one MP4 or MOV video of up to 30 minutes on its own; a request with a video can't include X accounts. A LinkedIn post with a video is published in the background, and get_publish_status reports it. See the Threads, X, and LinkedIn guides.

LinkedIn posts can also take a first comment, optionally with one image, and a link preview card for a web page through linkedinOptions. Try “Share this article on my LinkedIn as a link card and put the hashtags in the first comment.” See the LinkedIn guide.

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; if the first post ends up empty, the entire request fails with VALIDATION_ERROR before anything is published or scheduled. Put links in replies to share them, or set xOptions.keepFirstPostLink to true to keep them in the first post. If X recognizes a kept link, the post is charged as a post with a link. See X examples and scheduling scope.

Publishing or scheduling to X uses the organization's credits: 2 per post and 20 per post with a link, counted after first-post links are removed. A schedule is charged when it's created, and cancel_scheduled_post refunds it. If the organization doesn't have enough credits, the tool returns INSUFFICIENT_CREDITS and nothing is published or scheduled. See X credits.

New files follow create_media_upload → PUT bytes to the returned URL → confirm_media_upload. JPEG images up to 8 MiB are stored unchanged; PNG and WebP images up to 20 MiB are converted to JPEG during confirmation. Videos over 2 GiB, up to 4 GiB, use uploadMethod: "multipart": PUT each returned part to its own URL, then confirm. PDF, PPT, PPTX, DOC, and DOCX documents up to 100 MiB use mediaType: "DOCUMENT" and a single PUT; confirmation checks the contents: a PDF must open and have at most 300 pages, a PPTX or DOCX must be a PowerPoint or Word package, and a PPT or DOC must be an Office binary file. list_media with mediaType: "DOCUMENT" lists them. 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.

If the file is already online, try “Add this image to my Posteady media library: https://…”. import_media_from_url downloads the file from its link and returns the confirmed media, including its mediaId, in one call. The link must download the file itself; a web page such as a social media post doesn't work, and neither does a link that needs signing in. It accepts JPEG, PNG, and WebP images up to 20 MiB and MP4 and MOV videos up to 200 MiB. JPEG images up to 8 MiB are stored unchanged, and other images are converted to JPEG. Each call stores a new copy. See the import reference for the same rules over REST.

In ChatGPT, try “Post the image you just made to my Threads account.” save_chat_images saves images attached to or generated in the conversation to the media library: ChatGPT passes each file with a temporary link, and Posteady converts it to JPEG (up to 2160 px on the long side) and returns a mediaId. Saved images have public URLs, like other confirmed media. Other AI clients cannot pass conversation files, so they do not show this tool.

For asynchronous publishing, pass the returned jobId to get_publish_status. At unknown, inspect the target platform; do not automatically create another publishing request.

A Threads thread with more than one post is published the same way as Publish now in the Posteady app: publish_post publishes the first post during the call and the rest in the background, about 10 seconds per post. The Threads account's result has status: "processing" and a jobId; get_publish_status lists the posts published so far in postIds and reports published when the whole thread is up. X threads are published during the call, except a thread whose replies carry images through mediaIdsByPost: it is published the same way as a Threads thread. When the first Threads post carries a video, publish_post publishes nothing during the call: Threads processes the video in the background, the result has status: "processing", a jobId, and no postIds yet, and get_publish_status reports the post when it is up.

Carousels

Ask for something like “Turn this article into a carousel” and create_carousel submits the request with exactly one source: a topic (topic), source text (text), or a link (url). Posteady writes the copy for each slide and designs it, and one generation is charged to the organization’s credits. Photo slots use stock photos, the template’s own images, or no photos (imageMode). AI image generation is available in the Posteady app and the REST API, not through MCP. To use a specific template or brand, look up its ID with list_carousel_options first.

Generation usually takes one to three minutes. create_carousel returns only a carouselId, so call get_carousel until the status is completed or failed. A completed carousel returns the editor URL, a caption, and the mediaId of each rendered slide in order. Pass those IDs as instagram media to publish_post or schedule_post to publish or schedule the slides without further editing. If generation fails, its generation credits are refunded.

Calling again with the same requestId returns the same carousel without another charge. Use a new requestId only for a new carousel. Videos in the source are used as still images; video slides are created in the Posteady app. Inputs and failure codes are covered in the carousel guide.

Posts for several channels

Try “Write posts for my Threads and LinkedIn accounts from this article: https://…”. create_channel_texts writes a post for each selected account from one source: text (text), a public link (url), or one of your published posts (post). Each post is written in the voice of the account's persona and in its platform's format, the same way as Multiple channels at once in the Posteady app. List one account per platform in targets; each account needs an active persona. The call waits until the posts are written, which usually takes 10 to 30 seconds.

Posteady doesn't save or publish the result. Pass each channel's posts to publish_post or schedule_post with that account: X and Threads get a thread chain, and other platforms get one post. Instagram, TikTok, and YouTube still need media, and YouTube needs a title. Each written channel costs 5 credits, and a link source costs 5 more credits once per call. Channels that fail are listed in failed and aren't charged. Inputs and failure codes are covered in the channel posts guide.

Comments

Try “Show this week's unanswered comments” or “Reply to the latest comment on my Instagram post.” list_comments reads comments already synchronized to Posteady, with the same filters and statuses as the comment inbox: unanswered, replied, or resolved. It doesn't refresh the platforms. Results include each commenter's username and comment text. Without workspaceId, it returns the first page of every workspace where you can view comments, and workspaces lists the workspaces that have more pages with their nextCursor; pass that workspaceId and cursor to read further.

reply_to_comment posts a text reply as the account that received the comment, and hide_comment hides another person's comment or shows it again. delete_comment deletes your own comments on every platform and other people's comments on Instagram and Facebook. Pass commentId, platform, and accountId from list_comments, plus postId for LinkedIn. Replies and deletions take effect on the platform right away and can't be undone in Posteady. If a reply returns PLATFORM_ERROR or times out, check the platform before you send it again. See Read and reply to comments for platform differences.

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.

To change a scheduled post, try “Move tomorrow's Instagram post to Friday and use this caption instead.” replace_scheduled_post takes the same input as schedule_post, plus the original scheduledPostId and platform. accountIds must be the original post's account. Posteady creates the new schedule first and cancels the original only after the new one is accepted, so a failed replacement leaves the original as it is (replaced is null). If the original starts publishing before it can be canceled, the new schedule is canceled and the tool returns POST_NOT_CANCELLABLE. Media posts need a new requestId. See Replace a scheduled post.

Try “Show my recent posts with the highest views.” list_posts reads the last 90 days by default and returns up to 100 posts per call. Pass since and until (ISO 8601 with a timezone offset) to read another period of up to 90 days. totalMatched counts every post in the period, and when hasMore is true, offset reads the next page. Across workspaces, paging covers the first 100 posts; pass workspaceId to page further in one workspace (offset up to 9,900). A report on a whole period should read every page first.

For account-level numbers, try “How did my follower counts change last month?” get_account_analytics returns each account's follower change and the performance of its posts in the period, with the same definitions as the Posteady analytics page. previous holds the same metrics for the period of equal length right before it. Follower values come from daily snapshots, which exist only for Threads, X, Instagram, and LinkedIn. Workspaces where you can't view analytics are skipped and listed in note. See Account analytics.

Platform examples · Upload workflow · Schedule and cancel · Metric semantics

More related guides

On this page