content_posts_get

Tool

content_posts_get

Read one post: its current text, status, version numbers and outputs — one entry per output with its state (none, open, uncertain, failed, published, skipped) and the publication that decides it.

Read one post: its current text, status, version numbers and outputs — one entry per output with its state (none, open, uncertain, failed, published, skipped) and the publication that decides it. The way to re-read a post mid-run — after a wait, after an approval, after a publication settled.

Behavior

HTTP: GET /content/posts/:id

Arguments

Name	Type	Required	Description
id	string	•	The post id returned by content_posts_create.

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

Read one post: its current text, status, version numbers and outputs — one entry per output with its state (none, open, uncertain, failed, published, skipped) and the publication that decides it.

When to use

Example

Ask your agent something like this:

Read one post: its current text, status, version numbers and outputs — one entry per output with its state (none, open, uncertain, failed, published, skipped) and the publication that decides it.

The agent will invoke content_posts_get with these arguments:

{
  "id": "<id>"
}