---
title: "Call posts.plan_context"
method: POST
path: "/api/v1/tools/posts.plan_context"
tags: ["posts"]
---

# Call posts.plan_context

`POST /api/v1/tools/posts.plan_context`

## Request

- Base URL: `https://app.goosybear.ai`
- URL: `https://app.goosybear.ai/api/v1/tools/posts.plan_context`
- Auth: HTTP bearer

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.

## Headers

- `x-request-id` string

## Request body

- object
  - `piece_format` 'posts' | 'stories' | 'shorts_clips' | 'long_form' | 'articles' | 'podcast', nullable: Which format's destination catalogue to return. Omit for `posts` — carousels and single posts, the common case. Only pass another when the brief is explicitly about stories, shorts/clips or long form.
  - `days_ahead` integer, nullable: How many days of open cadence slots to read, from now. Omit for 7 ("this week"). Raise it only when the brief names a longer span.
  - `workspace` string: 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 `200`

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.

- union
  - object: The tool ran and answered.
    - `ok` true, required
    - `display_time_zone` string, nullable, required: The workspace's zone; every time here is UTC and renders in it.
    - `open_slots` object[], required
      - `slot_id` string, required
      - `destination` string, required
      - `publish_at` string, required
      - `status` string, required
      - `filled` boolean, required: Something is already bound to this slot.
    - `finals` object[], required
      - `source_ref` string, required: The finished video's id.
      - `title` string, required
      - `status` string, required
      - `bound_publish_at` string, nullable, required: When a cadence slot has it going out, or null.
    - `electable_platforms` string[], required: The destinations a piece of this format may be put on.
    - `workspace` string, required: The slug of the workspace this call ran in.
    - `working_in` object, required: Which workspace this call ran in, and how that was decided. Present on every workspace-scoped result.
      - `label` string, required: The chip words — e.g. "working in: Acme Main".
      - `note` string, required: Why this workspace — e.g. "your default", "this call only".
      - `workspace` string, required: The resolved workspace's slug.
      - `source` 'call-override' | 'key-pin' | 'stored-default' | 'sole-reachable', required: Which rung of the R7 precedence resolved the workspace.
  - ToolRefusal: A call that was admitted and dispatched, and did not succeed.
    - `ok` false, required
    - `code` string, required: The typed reason — e.g. `workspace_ambiguous`, `invalid_arguments`, or the tool's own failure code.
    - `message` string, required: A sentence a person can act on.
    - `workspaces` string[]: On a workspace refusal: the slugs this key may pass as `workspace`.
    - `issues` object[]: On `invalid_arguments`: which fields failed, and why.
      - `path` string, required
      - `message` string, required
    - `path` string: On an authoring refusal: where in your call's input it points, e.g. `steps.<key>.params.<field>`.
    - `fix` string: On an authoring refusal: the change to your call that would pass.
    - `instruction` string: On an authoring refusal: what to do next with it.

## Other responses

- `400`: The request could not be used: the body is present but not a JSON object (`tenant_api.malformed_body`); it is a top-level array carrying more messages than this endpoint accepts (`tenant_mcp.batch_too_large`); or the `Idempotency-Key` header is malformed (`tenant_api.idempotency_key_invalid`), disagrees with the body's `idempotency_key` (`tenant_api.idempotency_key_conflict`), or was sent to an action that cannot replay a retry (`tenant_api.idempotency_unsupported`). Nothing ran.
- `401`: No bearer credential, or one that did not resolve. Deliberately ONE undifferentiated answer for absent / unknown / revoked / expired, so the endpoint is never an oracle over the key space.
- `403`: The credential is good but the surface is not open to it — the platform or account API switch is off, or the holder lacks the `api.access` capability. The `code` says which.
- `404`: No such tool. The body names no tool and is identical for every unrecognised name.
- `429`: Over this key's per-minute cap. Carries `Retry-After` and `error.retry_after_seconds`.

---

[API](https://skmtc.dev/goosybear/apis/goosy-bear-api.md) · [All operations](https://skmtc.dev/goosybear/apis/goosy-bear-api/llms.txt) · [OpenAPI document](https://skmtc.dev/goosybear/apis/goosy-bear-api/revisions/6d82fb124064?raw)