content

Call content.status

Read where this workspace's content stands — 'what's scheduled this week?', 'why did that post fail?' — every piece with its lifecycle status, its schedule, its elected platform versions, and the reason any of it failed. Call this before answering any question about what is drafted, ready, scheduled or live; never guess it. It reads only. Not for the week laid out by day — that is schedule.read.

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/content.status

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/content.status
  • 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

status'draft' | 'variants_in_progress' | 'ready' | 'approved' | 'scheduled' | 'publishing' | 'published' | 'verified' | 'failed'

Only pieces in this lifecycle state.

format'posts' | 'stories' | 'shorts_clips' | 'long_form' | 'articles' | 'podcast'

Only pieces of this format.

limitinteger

How many pieces to return, newest-updated first.

cursorstring

Where to continue: pass the next_cursor from the previous page, with the same filters. Omit it for the first page.

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.