Call content.create_request
Ask this workspace to make a new piece of content on a given day — 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.
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
What kind of piece to create a request for.
posts, stories, shorts_clips, long_form The day it is planned for, as YYYY-MM-DD. The workspace's own cadence decides the time of day.
^\d{4}-\d{2}-\d{2}$A working title. Omit to leave it untitled.
1 - 200Which 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.
posts, stories, shorts_clips, long_form When it is planned to publish, ISO 8601 UTC.
The publication week it grouped under, when the workspace has one open.
True when it filled a slot the workspace's cadence already planned.
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.