splash_pad

Call splash_pad.write_article

Draft an article for the member — 'write me a blog post about this', 'draft an article on that topic', 'put together a write-up for the website'. You write the words: pass the headline they asked for and the body as markdown. It saves the draft as a document in the project they are working in (the one they name with board_id, else the one this conversation is about, else their Splash Pad) and hands back a link to the article's workflow, where THEY mark it final, make it a piece and publish it — this tool does none of those and never publishes anything. Not for putting a finished article on a site's blog — that is page.write_article.

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/splash_pad.write_article

Request

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

titlestring required

The headline, as the operator would write it. REQUIRED — nothing is derived from the body, because an article published without a real title reads as “(no title)” to readers.

body_markdownstring required

The article itself, in markdown. Headings, bold, italic, lists and links are kept; anything else arrives as its text.

board_idstring uuid

The project to put it in, when the operator names one: its board_id from something you were shown. Leave it out and it lands in the project they are working in, else their Splash Pad.

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.