Call posts.plan_context
Read what a posting plan has to work with — 'what slots are open this week', 'which finished videos could we post from', 'where can a carousel go'. It returns the workspace's open cadence slots over the next days (and whether each is already filled), the finished videos in its library with the date a slot binds each to, the destinations a piece of the chosen format may go to, and the zone every time renders in. It reads only and changes nothing. Not for one piece's own state — that is posts.api_read_piece.
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.
Request
- Base URL: https://app.goosybear.ai
- URL: https://app.goosybear.ai/api/v1/tools/posts.plan_context
- Auth: HTTP bearer
Headers
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
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.
Changes
No recorded changes to this operation across all 5 revisions of this API.