content_posts_skip_output

Tool

content_posts_skip_output

Mark one output of an approved post as "won't publish": it counts as closed, so a post whose other outputs are all published becomes published.

Mark one output of an approved post as "won't publish": it counts as closed, so a post whose other outputs are all published becomes published. It is not a content edit — no new version, the approval stands — and content_posts_unskip_output undoes it. Only past approval (409 post_not_approved otherwise). Refused with 409 output_has_live_publication while the output has a queued or in-flight publication (cancel it first), 409 already_published once it is out, 409 may_already_be_live while a finished publication of it may be live, 409 variant_not_found for an unknown output. Schedule, publish and record of a skipped output answer 409 output_skipped.

Behavior

HTTP: POST /content/posts/:postId/skip-output

Arguments

Name	Type	Required	Description
postId	string	•	The post id returned by content_posts_create.
variantId	string	•	The output to act on: a targets[].id (or outputs[].variantId) from content_posts_get.

Response

Field	Type	Always	Description
id	string	•	Post id.
text	string	•	The current text of the post, in markdown.
media	array	•	Media references attached to the current version.
notes	string	•	Private plan notes, or null when unset.
title	string	•	Plan title, or null when unset.
author	string	•	Identity id of whoever composed the post.
status	string	•	Post lifecycle status: idea (may have no text) -> draft (being written) -> pending_approval (submitted) -> approved (cleared to publish). Past approval the status follows EVERY output of the approved version (see outputs): scheduled while an output is queued or in flight and none is out yet; partially_published once some outputs are out and others are still queued, failed or never scheduled; published once every output is out; failed when an output gave up and none is out or queued; back to approved when nothing is live any more (all cancelled). A post in any of these five statuses can still have an output scheduled, including a failed one again.
outputs	array	•	One entry per output of this post, in targets order, with the state its publications add up to and the publication that decides it. Before approval every output is `none`. The post's status past approval is derived from exactly these states.
targets	array	•	The outputs of this post — a network and a variant each; several may share a network.
folderId	string	•	Folder containing this post, or null.
position	integer	•	Order within its folder, or null for an unfiled post.
createdAt	string	•	ISO-8601 creation time.
updatedAt	string	•	ISO-8601 time of the last change.
currentVersion	integer	•	Version number of the current text.
approvedVersion	integer	•	The version an approval binds to, or null. Cleared on every edit: approving one text never covers another.

Try it

Mark one output of an approved post as "won't publish": it counts as closed, so a post whose other outputs are all published becomes published.

When to use

Example

Ask your agent something like this:

Mark one output of an approved post as "won't publish": it counts as closed, so a post whose other outputs are all published becomes published.

The agent will invoke content_posts_skip_output with these arguments:

{
  "postId": "<postId>",
  "variantId": "<variantId>"
}