content

Call content.create_request

Ask this workspace to make a new piece of content on a given day — 'add a post on Thursday', 'we need something going out next Monday'. It is the same request the operator makes by pressing the plus in a cell of the schedule grid: it lands in that week's block, on the cadence's own planned slot when one is free, with the platforms that cadence elects. Not for reading what is already planned — 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.create_request

Request

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

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

What kind of piece to create a request for.

daystring required

The day it is planned for, as YYYY-MM-DD. The workspace's own cadence decides the time of day.

titlestring

A working title. Omit to leave it untitled.

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 5 revisions of this API.