posts

Call posts.read_piece

Read where one post piece stands — 'is this post ready to send', 'what's still missing on this piece', 'when does it go out'. It returns the piece's copy, its destinations and their versions, its publish time, the steps it still needs and whether its approval was sent. It reads only and changes nothing. Not for the workspace's whole pipeline at once — that is content.status.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/posts.read_piece

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/posts.read_piece
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

piece_idstring uuid required

The piece's id, as content.create_request, content.status or schedule.read return it.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 4 revisions of this API.