Call content.status
Read where this workspace’s content stands — 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.
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.
Authorizations
An API key minted at Settings › API & MCP. Send it as Authorization: Bearer <key>. A key carries its holder's own permissions, resolved on every call — revoking a membership closes the key's reach immediately. Keep it in an environment variable (GOOSY_API_KEY), never in a committed file.
Body
Only pieces in this lifecycle state.
draft, variants_in_progress, ready, approved, scheduled, publishing, published, verified, failed Only pieces of this format.
posts, stories, shorts_clips, long_form How many pieces to return, newest-updated first.
1 <= x <= 100Which 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.
1Response
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.
- Option 1
- Option 2
The tool ran and answered.
How many of the returned pieces sit in each status.
True when more pieces matched than were returned.
The slug of the workspace this call ran in.
Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.