schedule

Call schedule.read

Read one week of this workspace's schedule grid — 'what's going out next week?', 'show me Thursday's slots' — the format rows the active cadence plans, every piece bucketed into its day column, and the zone those columns are in. It is the same grid /schedule draws, so the answer and the screen always agree, and it reads only. Not for each piece's lifecycle status and failure reasons — 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/schedule.read

Request

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

weekstring

Any date in the wanted week, as YYYY-MM-DD. Omit for the current week.

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.