Tools reference

The TryPost MCP server exposes 83 tools. This page lists all of them, grouped like the app: posts, ideas, analytics, social accounts and the queue, repurpose, labels, signatures, webhooks, API keys, workspace and platform rules. Tool names are exactly what your assistant sees (kebab-case with a -tool suffix). Every tool acts on the one workspace you picked when you authorized the connection. Times in arguments are ISO 8601 (without an offset they are read as UTC). In responses, post, idea, label, signature, note and workspace times are UTC Y-m-d H:i:s; webhooks, API keys, repurposes, free slots and the upload expires_at are ISO 8601 with an offset.

There is no MCP tool that writes a caption, an image or a video for you. Your assistant writes the text itself and sends it with create-post-tool; the built-in AI writing assistant is available in the web app. Repurpose may shorten captions with AI in the background, including for rules created through MCP.

Recommended workflow

Create and publish a post

get-workspace-tool: check me.requires_approval. When it is true, anything you schedule, queue or publish waits for approval (see Approvals).
list-social-accounts-tool: pick the channel. Note its max_content_length, timezone and has_posting_schedule.
Settle the time zone. Times you say in conversation (“tomorrow at 9am”) are local, but every tool takes UTC and no tool returns your own time zone. Tell the assistant your time zone, or let it use the channel’s timezone from the previous step. It must send scheduled_at with an offset or in UTC.
list-content-types-tool: pick a content_type and read its media rules, hashtag limit and required_meta.
Resolve required settings: get-tiktok-creator-info-tool (TikTok privacy_level), list-pinterest-boards-tool or create-pinterest-board-tool (Pinterest board_id), list-discord-channels-tool (Discord channel_id).
Get media in: a public URL goes straight into media[]. For a local file, call request-media-upload-tool, upload the file with curl -F media=@file "<upload_url>" within 15 minutes (a CLI agent can run it; in a web or mobile chat you run it yourself), then pass the upload_token. Chat apps that run in the cloud can only use files at a public URL or the id of media already in TryPost.
create-post-tool (one channel) or create-posts-tool (several channels, one post each). Send status: draft to review first, or scheduled / publishing to go straight out.
preview-post-tool: see the exact text each network gets.
publish-post-tool: publish a draft now, at a time, or into the queue.
get-post-metrics-tool: read the saved analytics after it is published.

Use the queue

get-posting-schedule-tool: see the channel’s posting times (set them with update-posting-schedule-tool, generate-posting-schedule-tool or copy-posting-schedule-tool if it has none).
Create with status: scheduled and queue: next (first free slot) or queue: top (first slot, shifting queued posts back).
To take one exact slot: list-free-slots-tool, then create-post-tool with queue_slot, or move-post-to-slot-tool for an existing post.
reorder-queue-tool: swap queued posts among the slots they already hold.

How the queue keeps slots is explained in Queue.

Access and permissions

MCP accepts every member of the workspace, not only admins (the REST API only accepts admin API keys). Each tool then checks the same permission as the matching page in the app:

Who	Can call
Any member	Every Posts tool except approve, reject and set recurrence (including notes and media); ideas and idea stages; analytics; labels; signatures; `list-social-accounts-tool`, `get-posting-schedule-tool`, `list-free-slots-tool`, Pinterest boards, Discord channels, Instagram audio, TikTok creator info; `get-workspace-tool`; `list-content-types-tool`
Members who publish directly (owner, admins, and members who do not need approval)	`approve-post-tool`, `reject-post-tool`, `set-post-recurrence-tool`, `reorder-queue-tool`, `move-post-to-slot-tool`, every repurpose tool (reads included)
Admins (and the account owner)	`update-posting-schedule-tool`, `generate-posting-schedule-tool`, `copy-posting-schedule-tool`, every webhook tool and every API key tool (reads included)

A refused call returns a tool error such as This action is unauthorized. Items from another workspace answer as not found (Post not found., Repurpose not found., …). See Members and permissions.

Approvals

A member who needs approval can create and edit posts. When they schedule, queue or publish, TryPost stores the post with status pending_approval instead, and it waits for approve-post-tool or reject-post-tool from a member who publishes directly. The same happens when such a member edits an approved scheduled post or attaches media to it. A pending post is visible only to approvers and to the member who asked. A member who needs approval may delete only posts they wrote, or their own requests that are still pending. See Approvals.

Posts

Tool	What it does	Key arguments
`list-posts-tool`	List posts, newest scheduled date first. Read-only. REST: List posts	`status` (`draft` \| `scheduled` \| `pending_approval` \| `published` \| `failed`), `search` (substring of the text), `channels[]`, `labels[]`, `untagged`, `page`
`get-post-tool`	Get one post: text, media, labels, status, `schedule_mode`, `scheduled_at`, `published_at`, recurrence, approval fields, `origin`, `post_group_id`, and its channel at the top level: `publish_status`, `platform`, `content_type`, `meta`, `error_message`, `platform_url` and `social_account`. Read-only. REST: Get post	`post_id` (required)
`create-post-tool`	Create one post on one channel: a draft, a post at a custom time, a queue post (next or top, or one exact free slot), or a post published now. Returns the post. REST: Create post	`social_account_id` (required), `content_type`, `meta`, `content`, `media[]`, `status` (`draft` default \| `scheduled` \| `publishing`), `scheduled_at`, `queue` (`next` \| `top`), `queue_slot`, `label_ids[]`
`create-posts-tool`	Create one independent post per destination, as the composer does with several channels; the posts share a `post_group_id`. Each destination may override text, media, type and meta. No `queue_slot` here. Returns `{posts}`. REST: Create posts in batch	`status` (required), `destinations[]` (required: `{social_account_id, content_type?, content?, media?, meta?}`), `content`, `media[]`, `scheduled_at`, `queue`, `label_ids[]`
`update-post-tool`	Change a post’s text, media (replaces the list), `content_type`, `meta` (merged; `null` clears a key, `thread_replies` replaces the list), status, schedule, queue or labels. The channel itself is fixed. On Pinterest and TikTok, new media re-decides the type when `content_type` is omitted. REST: Update post	`post_id` (required), `content`, `media[]`, `content_type`, `meta`, `status` (`draft` \| `scheduled` \| `publishing`), `scheduled_at`, `queue`, `label_ids[]`
`publish-post-tool`	Publish a draft or scheduled post now, at `scheduled_at`, or into the queue. Validated like a scheduled post (text limits, required meta, media rules, thread replies); a failure names the platform and field and nothing is published. Destructive. No single REST operation: REST uses Update post with a status	`post_id` (required), `scheduled_at`, `queue`
`approve-post-tool`	Approve a `pending_approval` post. By default it is scheduled as its author asked (queue or requested time); pass a new time or publish now instead. One of them is required when the requested time has passed or the author asked to publish now. Pass one of `scheduled_at` (future, before 2038-01-19) or `publish_now`, not both. Destructive. REST: Approve post	`post_id` (required), `scheduled_at`, `publish_now`
`reject-post-tool`	Reject a `pending_approval` post. It goes back to drafts and the member who asked is emailed; no reason is stored. REST: Reject post	`post_id` (required)
`preview-post-tool`	Show the exact text the post’s network gets (X links defused when that is on), next to the original, with length stats. An X poll, and each reply poll, comes with its `poll`. One object, with `platform` and `content_type` at the top. Nothing is truncated. Read-only. REST: Get post preview	`post_id` (required)
`delete-post-tool`	Delete a post from TryPost permanently. It is never removed from the network. Returns `{deleted: true}`. Destructive. REST: Delete post	`post_id` (required)
`attach-media-from-url-tool`	Download files from public URLs and append them to the post. Returns `post`, `attached_count`, `failed_urls` and `failures[]` with a reason (`unreachable`, `type_not_allowed`, `too_large`, `host_not_allowed`). REST: Attach media from URL	`post_id` (required), `urls[]` (required, 1–10 `{url, alt?}`)
`request-media-upload-tool`	Issue a one-time signed URL to upload a local file. Returns `upload_token`, `upload_url`, `expires_at`, `max_bytes`, `max_bytes_by_type` and `field_name` (`media`). Upload with `curl -F media=@file "<upload_url>"`. REST: Upload to signed URL	none
`attach-media-from-upload-tool`	Append an uploaded file to a post. Returns `{post}`. REST: Attach media from upload	`post_id` (required), `upload_token` (required), `alt`
`get-post-metrics-tool`	Read the latest saved analytics of a published post (reactions, comments, saves, reach, views, watch time where supported). Returns one object: `post_id`, `platform`, `publish_status`, `platform_post_id`, `platform_url` and `metrics`. Values may lag the network until the next analytics run; an unpublished post or a network without analytics answers `unsupported`. An X poll’s votes are in `metrics.publication.poll`, and reply polls in `metrics.publication.thread_polls`. Read-only. REST: Get post metrics	`post_id` (required)
`list-post-notes-tool`	List a post’s notes (internal team comments, never published), newest first. Read-only. REST: List post notes	`post_id` (required), `page`
`create-post-note-tool`	Add a note. Every other member who has note emails on is emailed; on a pending post, only the approvers and the member who asked. REST: Create post note	`post_id` (required), `body` (required, max 2000)
`update-post-note-tool`	Edit a note. Only its author can. No email is sent. REST: Update post note	`post_id`, `note_id`, `body` (all required)
`delete-post-note-tool`	Delete a note. Only its author can. Destructive. REST: Delete post note	`post_id`, `note_id` (both required)
`set-post-recurrence-tool`	Make a scheduled post repeat every `interval` days, weeks, months or years, `times` more times, at the same local time in the channel’s zone. The last occurrence must be on or before 2037-12-31 23:59:59 UTC. Members who publish directly only. REST: Set post recurrence	`post_id`, `interval` (1–365), `frequency` (`day` \| `week` \| `month` \| `year`), `times` (1–100), all required
`clear-post-recurrence-tool`	Stop a post from repeating. The post and its next time stay. REST: Remove post recurrence	`post_id` (required)

Posts that are publishing, published or failed cannot be changed or deleted. Notes and recurrence follow Recurring posts.

Before a post can be scheduled or published

Drafts may be incomplete. Scheduling, queueing or publishing needs:

Text or media.
TikTok meta.privacy_level, one of the privacy_level_options from get-tiktok-creator-info-tool.
Pinterest meta.board_id and Discord meta.channel_id.
Google Business: meta.event with a title and start/end dates on EVENT and OFFER (the end may not precede the start). A call_to_action needs a url unless its action_type is NONE or CALL, and offers take no call to action.
Thread replies (X, Bluesky, Mastodon): each reply that is not a poll has text or media, and each reply fits the account limit. On LinkedIn, at most one reply (the comment), with text and no media.
YouTube: a title (meta.title, or the first line of the text).
X poll (x_poll, or a reply with poll): a question, at least 2 poll.options and poll.duration_minutes.

list-content-types-tool lists the unconditional ones (TikTok, Pinterest, Discord) per platform as required_meta. Media rules (count, size, duration, aspect ratio, GIF and MOV) are checked at the same moment, never on a draft. The exception is X polls: on an x_poll post or a reply poll, media, a repeated choice, more than 4 choices, a choice over 25 characters or a duration_minutes outside 5–10080 is refused on every save, drafts included.

Media

Every media[] item gives exactly one of:

Key	Use
`url`	A public `http(s)` URL that serves the file itself. Redirects are not followed and web pages are refused; the download must finish within 20 seconds.
`upload_token`	A file uploaded with `request-media-upload-tool`. A token is spent by the first post that takes it; uploads are kept 24 hours.
`id`	A media item already in this workspace (from a post’s `media`). It is copied for the post. On update, send the current ids in a new order to reorder, and leave one out to remove it.

Optional per item: alt (images), and meta with alt_text (max 2000; it wins over alt), user_tags (Instagram feed images, up to 20 {username, x, y}) and cover_offset_ms (video cover frame, where supports_video_cover). attach-media-from-upload-tool and attach-media-from-url-tool take the same alt and meta. A PDF must be the only attachment. The first item is the cover of a carousel. Accepted files: JPEG, PNG, GIF and WebP images (HEIC and HEIF when the server can convert them), MP4 and MOV videos, and PDF. Server ceilings by default: 10 MB and 67 megapixels per image, 1 GB per video, 100 MB per PDF. Each network’s own, usually smaller, limits apply when the post is scheduled or published. The signed upload URL works once and expires after 15 minutes. More in Media uploads.

Per-platform `meta`

meta holds the settings of the post’s channel. The same keys work on the REST API (Posting guide). Unknown keys are dropped. Enum values are exact JSON strings.

Platform	Keys	Required to schedule or publish
X, Bluesky, Mastodon	`thread_replies`: up to 24 replies published under the post, each `{text, media}` (up to 4 media items per reply) or a plain string. Each reply fits the account’s text limit. X also takes `is_ai_generated`	—
X	`poll` on content type `x_poll`: `{options, duration_minutes}`, 2 to 4 different choices of 1–25 characters and 5–10080 minutes. The post text is the question (max 280, even with long posts). A poll takes no media, drafts included, and media tools refuse to attach to one. `poll` is merged key by key on update; `options` replaces the list. A reply in `thread_replies` can be `{text, poll}` under the same rules	`poll.options` (2 or more), `poll.duration_minutes` and a question
Mastodon	`spoiler_text` (content warning, max 500; counts toward the 500 characters and is repeated on every reply)	—
TikTok	`privacy_level` (`PUBLIC_TO_EVERYONE` \| `MUTUAL_FOLLOW_FRIENDS` \| `FOLLOWER_OF_CREATOR` \| `SELF_ONLY`); `allow_comments`, `disclose`, `brand_content_toggle`, `brand_organic_toggle`; on `tiktok_video` also `allow_duet`, `allow_stitch`, `is_aigc`; on `tiktok_photo` also `auto_add_music`. `SELF_ONLY` cannot be combined with `brand_content_toggle`	`privacy_level`
Pinterest	`board_id`, `title` (max 100), `link`	`board_id`
Discord	`channel_id`, `mentions` (`[{token, label}]`), `embeds` (up to 10 `{title, description, url, image, color}`). The channel name is filled by TryPost from the channel list read in the last 5 minutes; a `channel_name` you send is ignored	`channel_id`
YouTube	`title` (max 100, no `<` or `>`), `description` (max 5000 bytes), `category_id` (default `22`), `privacy_status` (`public` \| `unlisted` \| `private`), `license`, `notify_subscribers`, `embeddable`, `made_for_kids`, `is_ai_generated`	A title, or text to derive it from
Instagram	`is_ai_generated`; `collaborators` (up to 3 usernames, feed posts, carousels and reels, not stories; the post shows on a collaborator’s profile only after they accept the invite in the Instagram app, and a username that does not exist is only refused when the post publishes); on `instagram_reel` also `share_to_feed` (default `true`), `trial_graduation` (`MANUAL` \| `SS_PERFORMANCE`, not with `collaborators`, only on accounts where Instagram offers trial reels) and `audio` (`instagram-facebook` accounts only: `{id, title, artist, cover_url, preview_url, audio_volume, video_volume}`, `id` from `search-instagram-audio-tool` as a string of digits, volumes 0–100, default 100). People tags and a video cover are per media item (see Media). At most 5 hashtags	`audio.id` when `audio` is set; no `collaborators` on a trial reel
Threads	`topic_tag` (1–50 characters, no `.` or `&`). Content type `threads_ghost_post` is a text-only post archived after 24 hours	—
Facebook, Bluesky, LinkedIn	`link_preview` (default `true`; `false` publishes the link without a preview card)	—
LinkedIn, LinkedIn Page	`document_title` (max 300, for PDF document posts); `thread_replies`: one text-only reply, published as a comment from the same profile or page (up to 3000 characters)	—
Google Business	`topic_type` (`STANDARD` \| `EVENT` \| `OFFER`), `call_to_action` `{action_type, url}`, `event` `{title, start_date, end_date, start_time, end_time}`, `offer` `{coupon_code, redeem_online_url, terms_conditions}`	`event` on `EVENT`/`OFFER`; `call_to_action.url` unless `NONE`/`CALL`. `action_type` is one of `NONE`, `BOOK`, `ORDER`, `SHOP`, `LEARN_MORE`, `SIGN_UP`, `CALL`; offers take no call to action
Telegram, Facebook reels and stories	none	—

Instagram and Facebook stories publish no text.

Ideas

Any member can use the ideas tools. Ideas cannot be turned into posts through MCP: create a post with the idea’s text instead. See Ideas.

Tool	What it does	Key arguments
`list-ideas-tool`	List ideas, newest first. Filters combine like the ideas board. Read-only. REST: List ideas	`stages[]`, `unassigned`, `labels[]`, `untagged`, `page`
`get-idea-tool`	Get one idea with its title, body, stage, media and labels. Read-only. REST: Get idea	`idea_id` (required)
`create-idea-tool`	Create an idea. It needs a title, a body or media. REST: Create idea	`title` (max 255), `body` (max 10000), `idea_stage_id`, `media_ids[]` (max 10, media already in the workspace), `label_ids[]`
`update-idea-tool`	Update an idea. Only sent fields change; `media_ids` and `label_ids` replace the lists. A new stage places it last. To move it to no stage use `move-ideas-tool`. REST: Update idea	`idea_id` (required), `title`, `body`, `idea_stage_id`, `media_ids[]`, `label_ids[]`
`delete-ideas-tool`	Delete up to 500 ideas with their media. Ids from other workspaces are ignored. Destructive. REST: Delete ideas	`idea_ids[]` (required)
`duplicate-idea-tool`	Copy an idea with its media and labels, right after the original. REST: Duplicate idea	`idea_id` (required)
`move-ideas-tool`	Move an idea to a stage (or none) and set that column’s order. A stale list is refused. REST: Move idea	`idea_id` (required), `idea_ids[]` (required: every idea of the target column in the new order), `idea_stage_id` (omit for no stage)
`list-idea-stages-tool`	List the board’s stages in order, with the number of ideas in each. Read-only. REST: List idea stages	none
`create-idea-stage-tool`	Add a stage at the end of the board. REST: Create idea stage	`name` (required, max 60)
`update-idea-stage-tool`	Rename a stage. REST: Update idea stage	`idea_stage_id`, `name` (both required)
`delete-idea-stage-tool`	Delete a stage. Its ideas move to the unassigned column. Destructive. REST: Delete idea stage	`idea_stage_id` (required)
`reorder-idea-stages-tool`	Reorder the stages. Returns `{stages}`. REST: Reorder idea stages	`stage_ids[]` (required: every stage, in the new order)

Analytics

Any member can read analytics. Ranges are calendar days in your time zone: range is 7d, 30d (default), mtd or custom (with start and end as YYYY-MM-DD). See Insights.

Tool	What it does	Key arguments
`get-analytics-report-tool`	The workspace report: summary, follower and post charts, top posts, per-account performance, data bounds and sync coverage. Unknown channel ids are ignored. Read-only. REST: Get workspace analytics	`range`, `start`, `end`, `channels[]`
`get-analytics-publication-tool`	All saved metrics and metadata of one publication from the report, including posts imported from the network. An X poll’s votes are in `publication.poll`, and reply polls in `publication.thread_polls`. Read-only. REST: Get publication analytics	`publication_id` (required)
`get-channel-insights-tool`	One channel’s summary, metrics and series for the range and the previous range of the same length, plus `growth` (monthly follower growth over 12 months). Not available for LinkedIn, LinkedIn Page, Telegram, Discord and Google Business. Read-only. REST: Get channel insights	`account_id` (required), `range`, `start`, `end`, `period`, `sort`, `labels[]`, `untagged`, `types[]`
`list-channel-publications-tool`	A channel’s best posts in the range, ranked by `sort` (top 50). Not available for LinkedIn, LinkedIn Page, Telegram, Discord and Google Business. Read-only. REST: List channel post performance	`account_id` (required), `range`, `start`, `end`, `period` (`current` \| `previous`), `sort` (`reactions` \| `comments` \| `engagement_rate` \| `views` \| `impressions` \| `shares` \| `saves` \| `reach`), `labels[]`, `untagged`, `types[]`, `page`

MCP cannot connect, disconnect or reconnect channels; do that in the app (Connecting channels).

Tool	What it does	Key arguments
`list-social-accounts-tool`	List connected channels: `id`, `platform`, `display_name`, `username`, `status` (`connected` \| `token_expired` \| `disconnected`), `timezone`, `posting_goal`, `has_posting_schedule`, `max_content_length`, `long_posts`, `verified_badge`. An X account with `long_posts` may post 25000 characters, others 280. Read-only. REST: List social accounts	`page`
`get-posting-schedule-tool`	A channel’s time zone, weekly goal and the seven days with their local posting times (day `0` is Sunday). Read-only. REST: Get posting schedule	`account_id` (required)
`update-posting-schedule-tool`	Replace a channel’s schedule. At most 4 unique `HH:mm` times per day. `null` clears it. Queued posts whose slot vanished are re-placed; a zone change keeps each queued post at the same local clock time. Admins only. REST: Update posting schedule	`account_id` (required), `timezone` (required, IANA), `posting_goal` (1–28 or `null`), `posting_schedule` (exactly 7 `{day, enabled, times[]}` or `null`)
`generate-posting-schedule-tool`	Generate a schedule from the network’s recommended windows for a weekly goal, replacing the current one. It also saves `goal` as the channel’s weekly goal. `mode` has no effect today. Admins only. REST: Generate posting schedule	`account_id` (required), `mode` (required, `goal` \| `recommended`), `goal` (1–28; default the channel goal, else 3)
`copy-posting-schedule-tool`	Copy another channel’s schedule onto this one. The source must have a schedule. Admins only. REST: Copy posting schedule	`account_id` (required), `from` (required)
`list-free-slots-tool`	The channel’s next free queue slots as UTC instants, soonest first: at most 30, within 90 days. Read-only. REST: List free queue slots	`account_id` (required)
`reorder-queue-tool`	Reorder a channel’s queue: the posts swap among the slots they hold. The ids must be exactly the first reorderable queued posts, otherwise the call is refused. Returns `{post_ids}`. Members who publish directly only. REST: Reorder queue	`account_id` (required), `post_ids[]` (required, max 500)
`move-post-to-slot-tool`	Move a scheduled post onto one free slot; it becomes a queue post there. Taken, off-schedule or pending-held slots are refused. Members who publish directly only. REST: Move post to queue slot	`account_id`, `post_id`, `slot_at` (all required)
`list-pinterest-boards-tool`	List a Pinterest account’s boards: `{boards: [{id, name, cover_url}], truncated}`. Use a board `id` as `meta.board_id`. REST: List Pinterest boards	`account_id` (required)
`create-pinterest-board-tool`	Create a board on a Pinterest account. Returns `id`, `name`, `cover_url`. REST: Create Pinterest board	`account_id` (required), `name` (required, max 50)
`list-discord-channels-tool`	List the text and announcement channels the bot can post to: `{channels: [{id, name}]}`. Use an `id` as `meta.channel_id`. REST: List Discord channels	`account_id` (required)
`search-instagram-audio-tool`	Search the music and original sounds an Instagram account connected through Facebook can put on a reel: `{audio: [{id, type, title, artist, cover_url, duration_ms, preview_url}]}`, music first. Omit `q` for trending audio; with `q`, music must name every word. Use an `id` as `meta.audio.id`, and copy its `title`, `artist`, `cover_url` and `preview_url` into `meta.audio` so the app shows the track. Answers are cached for 10 minutes; a workspace may make 30 uncached audio lookups per minute. An Instagram Login account returns an error. Read-only. REST: Search Instagram audio	`account_id` (required), `q` (max 100), `type` (`music` \| `original_sound`)
`get-instagram-audio-tool`	One audio track by id, with fresh `cover_url` and `preview_url` (Instagram expires them). Fails when the track is no longer available. Same account rule and lookup limit as the search. Read-only. REST: Get Instagram audio	`account_id`, `audio_id` (both required)
`get-tiktok-creator-info-tool`	What TikTok lets this creator publish now: `privacy_level_options`, `comment_disabled` / `duet_disabled` / `stitch_disabled`, `max_video_post_duration_sec`, `can_post`. `max_video_post_duration_sec` is not checked when you schedule, so compare the video length yourself. A TikTok posting limit or outage returns an error. Read-only. REST: Get TikTok creator info	`account_id` (required)

Repurpose

A repurpose watches one Instagram or Facebook account for one video format and republishes each new video to its destinations. Members who publish directly can use these tools. See Repurpose.

Tool	What it does	Key arguments
`list-repurpose-source-formats-tool`	List the formats a repurpose can watch (`reel`, `video`, `story`) with labels. Returns `{source_formats}`. Read-only. REST: List repurpose source formats	none
`list-repurposes-tool`	List the workspace’s repurposes. Read-only. REST: List repurposes	`page`
`get-repurpose-tool`	Read one repurpose: format, destinations, status and last polling error. Read-only. REST: Get repurpose	`repurpose_id` (required)
`create-repurpose-tool`	Create a repurpose as a draft. One repurpose per source and format; the source cannot also be a destination; Google Business cannot be a destination. Each destination picks a content type that accepts video. Thread-reply media in a destination’s `meta` may only be media `id`s. Required meta is re-checked on every update of an active repurpose. REST: Create repurpose	`source_social_account_id` (required), `source_format` (default `reel`), `publish_mode` (`publish` default \| `draft`), `destinations[]` (`{social_account_id, content_type, meta?}`)
`update-repurpose-tool`	Update a repurpose. Changing the source or format resets the watermark. `destinations` replaces the list. Thread-reply media in a destination’s `meta` may only be media `id`s. Required meta is re-checked on every update of an active repurpose. REST: Update repurpose	`repurpose_id` (required), `source_social_account_id`, `source_format`, `publish_mode`, `destinations[]`
`activate-repurpose-tool`	Start watching. Needs a usable source, at least one destination and the destinations’ required meta. Only videos published from now on are replicated. REST: Activate repurpose	`repurpose_id` (required)
`pause-repurpose-tool`	Pause an active repurpose; the watermark is kept. REST: Pause repurpose	`repurpose_id` (required)
`resume-repurpose-tool`	Resume a paused repurpose, with the same checks as activation. After a pause you made it continues from where it stopped; after a pause TryPost made (for example the source needed reconnecting) it starts from now, so videos posted meanwhile are not replicated. REST: Resume repurpose	`repurpose_id` (required)
`disable-repurpose-tool`	Turn a repurpose off and clear its watermark. REST: Disable repurpose	`repurpose_id` (required)
`list-repurpose-items-tool`	Every source video the repurpose has seen, with why each was skipped. Read-only. REST: List repurpose items	`repurpose_id` (required), `page`
`delete-repurpose-tool`	Delete a repurpose. Polling stops; posts it created stay. Returns `{deleted: true}`. REST: Delete repurpose	`repurpose_id` (required)

Videos already published through TryPost are never replicated.

Labels

Any member can manage labels. See Labels.

Tool	What it does	Key arguments
`list-labels-tool`	List the workspace’s labels. Read-only. REST: List labels	`page`
`create-label-tool`	Create a label. REST: Create label	`name` (required, max 255), `color` (required, `#RRGGBB`)
`update-label-tool`	Update a label’s name and color. REST: Update label	`label_id`, `name`, `color` (all required)
`delete-label-tool`	Delete a label and detach it from every post. Destructive. REST: Delete label	`label_id` (required)

Signatures

Any member can manage signatures. A signature is never added to a post on its own: append its content to the post text. See Signatures.

Tool	What it does	Key arguments
`list-signatures-tool`	List the workspace’s signatures. Read-only. REST: List signatures	`page`
`create-signature-tool`	Create a signature. REST: Create signature	`name` (required, max 255), `content` (required)
`update-signature-tool`	Update a signature. REST: Update signature	`signature_id`, `name`, `content` (all required)
`delete-signature-tool`	Delete a signature. Destructive. REST: Delete signature	`signature_id` (required)

Webhooks

Admins only. Each delivery is a JSON POST signed with HMAC-SHA256 of the body; the hex digest is in X-Webhook-Signature. After 5 failed deliveries in a row the webhook is paused and the account owner is emailed. Events: post.created, post.scheduled, post.unscheduled, post.published, post.failed, post.deleted. See Webhooks.

Tool	What it does	Key arguments
`list-webhooks-tool`	List webhooks without their secrets. Read-only. REST: List webhooks	`page`
`get-webhook-tool`	Get one webhook, including `signing_secret`. Read-only. REST: Get webhook	`webhook_id` (required)
`create-webhook-tool`	Create a webhook (always `enabled`). Returns it with `signing_secret`. Private or local endpoints are refused; no test request is sent. REST: Create webhook	`endpoint` (required, max 255), `events[]` (required, at least one)
`update-webhook-tool`	Update the endpoint, events or status. Re-enabling a paused webhook resets its failures. REST: Update webhook	`webhook_id` (required), `endpoint`, `events[]`, `status` (`enabled` \| `disabled`)
`delete-webhook-tool`	Delete a webhook and its logs. Destructive. REST: Delete webhook	`webhook_id` (required)
`send-webhook-test-tool`	Send a signed `webhook.test` ping. Writes no delivery log. Returns `{tested: true}`. REST: Send webhook test	`webhook_id` (required)
`rotate-webhook-secret-tool`	Rotate the signing secret; the old one stops working at once. Returns the new `signing_secret`. Destructive. REST: Rotate webhook secret	`webhook_id` (required)
`list-webhook-logs-tool`	List delivery logs, newest first, with payload and response body. Read-only. REST: List webhook logs	`webhook_id` (required), `page`
`replay-webhook-log-tool`	Queue a new signed delivery of a log’s payload, even when the webhook is paused or disabled. Returns `{replayed: true}`. REST: Replay webhook log	`webhook_id`, `log_id` (both required)

API keys

Admins only. These manage the Personal Access Tokens used by the REST API; OAuth connections such as this one are not listed. Each admin sees and revokes only the keys they created in this workspace. See API keys.

Tool	What it does	Key arguments
`list-api-keys-tool`	List API keys (metadata only, never the secret). Read-only. REST: List API keys	`page`
`create-api-key-tool`	Create an API key. Returns `{token, plain_token}`: `token` is the metadata and `plain_token` the secret, shown once. REST: Create API key	`name` (required, max 255), `expires_at` (today or later; omit for no expiry)
`delete-api-key-tool`	Revoke an API key. Integrations using it stop working. Destructive. REST: Delete API key	`api_key_id` (required)

Workspace

Tool	What it does	Key arguments
`get-workspace-tool`	The workspace this connection acts in (`id`, `name`, timestamps) and what you may do there: `me.is_admin`, `me.requires_approval`, `me.publishes_directly`. Read-only. REST: Get workspace	none

Platform

Tool	What it does	Key arguments
`list-content-types-tool`	Every platform with its content types and rules. Per platform: `label`, `allowed_media_types`, `default_content_type`, `max_content_length` (the network default; the account limit is in `list-social-accounts-tool`), `recommended_content_length`, `max_hashtags`, `alt_text_max_length`, `required_meta`. Per content type: `value`, `label`, `description`, media counts (`min_media_count`, `requires_media`), `forbids_mixed_media`, `auto_fits_image`, accepted types, GIF and MOV, byte caps, video duration, aspect ratios, image sizes, alt text, user tags, video cover, `captionless`, `document_must_be_alone`, `supports_thread_replies`, `max_thread_replies`. Call it before choosing a `content_type` or attaching media. Read-only. REST: List content types	none

Notes

Lists are paginated with the app page size (25 today; read per_page rather than assuming it). Pass page; responses carry total, per_page, current_page and last_page next to the rows.
Errors come back as tool errors with a message (Post not found., This action is unauthorized., or the validation message). When the queue of a channel is busy, retry in a moment.
Confirmations: every tool tells the client whether it only reads, whether it changes or removes existing data, and whether it reaches outside TryPost. Read-only tools run without asking in most clients. Tools that change or remove data, publish, approve or reject, send email or replay a webhook are marked destructive, so clients ask you first; purely additive tools (creating an idea, idea stage, label, signature, API key, repurpose, webhook or Pinterest board, and requesting an upload) are not. Tools that can publish to public networks, fetch a URL, call a webhook endpoint or read Instagram’s audio catalog are marked as reaching outside TryPost.
Not available through MCP: AI generation, connecting or disconnecting channels, turning ideas into posts, templates, members and invites, billing. Use the web app for these.

Getting Started

Setup Guides

Recommended workflow

Create and publish a post

Use the queue

Access and permissions

Approvals

Posts

Before a post can be scheduled or published

Media

Per-platform `meta`

Ideas

Analytics

Repurpose

Labels

Signatures

Webhooks

API keys

Workspace

Platform

Notes

​Recommended workflow

​Create and publish a post

​Use the queue

​Access and permissions

​Approvals

​Posts

​Before a post can be scheduled or published

​Media

​Per-platform meta

​Ideas

​Analytics

​Social accounts and queue

​Repurpose

​Labels

​Signatures

​Webhooks

​API keys

​Workspace

​Platform

​Notes

Recommended workflow

Create and publish a post

Use the queue

Access and permissions

Approvals

Posts

Before a post can be scheduled or published

Media

Per-platform `meta`

Ideas

Analytics

Social accounts and queue

Repurpose

Labels

Signatures

Webhooks

API keys

Workspace

Platform

Notes