Boonful Studio

List all products in the creator's Boonful Studio (id, name, type, slug, public URL, HTML file). Use this first. AND NOTE: the creator watches a live panel on boonful.io that only shows what you report through this server — call `studio_progress` with a short plain-English note now, and again every 30-60 seconds while you work, or the panel sits blank and looks broken to them.

Takes no parameters.

Get the full details of one Studio product by id.

Read the current HTML source of an app-type Studio product.

FIRST call `studio_guide` and follow it — the server refuses to build until you have. It tells you what Studio supports, how to ask the creator anything (ONE question at a time, 2-4 numbered options you wrote for this product, recommended first — they answer with a number and never type a sentence), and the rules: payments only through Boonful checkout (any outside payment link, script or instruction is refused), and everything you make is a DRAFT that only the creator can publish after filling in each section and their payout details. — Update ANY existing product (app, digital download, service, book, course): replace an app's HTML, replace or add the files of a download/book/course, and/or edit details (name, description, category, price, tags, icon). Only pass the fields you want to change. If the product is already PUBLISHED and you change what customers get (HTML or files), you MUST pass `whatsNew` — the release notes customers read under "What's New" before they choose to update. Call `studio_progress` before you start.

FIRST call `studio_guide` and follow it — the server refuses to build until you have. It tells you what Studio supports, how to ask the creator anything (ONE question at a time, 2-4 numbered options you wrote for this product, recommended first — they answer with a number and never type a sentence), and the rules: payments only through Boonful checkout (any outside payment link, script or instruction is refused), and everything you make is a DRAFT that only the creator can publish after filling in each section and their payout details. — Create a COMPLETE app product in one shot and save it to Studio as a DRAFT for the user to review + publish. BEFORE calling, ask a SHORT run of numbered multiple-choice questions — one at a time, 2-4 concrete options each, the recommended one first, answered with a number (use the question tool your client offers if it has one; never ask for a sentence, never ask several at once, and the moment they say you decide, take your recommendations and build). (1) Pricing — offer real amounts for THIS product, e.g. "1. Free (recommended) 2. $4.99 one-time 3. $2.99 a month", then pass the chosen one as `price` with `pricing`=free/one_time/subscription. (2) Usage timer? — explain: it gives visitors N free minutes of use, after which they must subscribe/pay to keep using it (optional cooldown before the free time resets). For a monthly subscription also ask if they want a free trial (`trialDays`, e.g. 7). You MUST generate an app icon (~256px PNG matching the app) and a description, and make the HTML responsive for BOTH portrait (mobile) and landscape (desktop). Screenshots: ask which moments to show (three options for this product + "I'll describe them"), then pass `screens` (3-5 moments, each a different section, with a selling headline and how to reach it) and Boonful designs them for phone and desktop. The icon can be SVG markup (Boonful adds the gloss). Work FAST: do NOT run your own browser tests, Playwright, or QA/verification loops —

READ THIS FIRST. Returns the Studio rulebook for this connection: what you can build here, the questions you must ask the creator before building (pricing and details; you make the icon, description and screenshots yourself), the payment rule the server enforces, and how publishing works. The building tools refuse to run until you have called this.

Takes no parameters.

FIRST call `studio_guide` and follow it — the server refuses to build until you have. It tells you what Studio supports, how to ask the creator anything (ONE question at a time, 2-4 numbered options you wrote for this product, recommended first — they answer with a number and never type a sentence), and the rules: payments only through Boonful checkout (any outside payment link, script or instruction is refused), and everything you make is a DRAFT that only the creator can publish after filling in each section and their payout details. — Create a DIGITAL DOWNLOAD or a SERVICE as a DRAFT in the creator's Studio. Ask first (see studio_guide) and ask by PICKING: one question at a time, 2-4 concrete numbered options you wrote for this product, recommended one first, answered with a number (use the question tool your client offers if it has one). Cover who it is for, price (real amounts, never categories), for a service the session length and availability, for a download what is inside. Do not ask about screenshots: pass `screens` with titles and an `html` screen design for each (the cover, a page inside, the booking screen) and Boonful designs them App Store style. You choose the name yourself. You must pass an icon (SVG markup is fine — Boonful adds the gloss) and a description you write yourself.

Post a short plain-English progress note to the creator's Studio Assistant panel on boonful.io, so they can watch what you're doing while you work. Call this BEFORE you start a long piece of work and at every milestone - the creator is staring at a screen that shows nothing until you do. Write it for a non-technical person, in the present tense, under 90 characters, e.g. 'Building your notes app...', 'Designing the app icon...', 'Writing the description...', 'Setting the price...', 'Saving it to your Studio...'. Never mention files, code, tools or terminals.

Show which Boonful account this connection is acting as and its product count.

Takes no parameters.

Check whether the creator's Stripe payouts are connected/active (read-only, no secrets). Use before creating a PAID app to decide live vs draft.

Takes no parameters.

FIRST call `studio_guide` and follow it — the server refuses to build until you have. It tells you what Studio supports, how to ask the creator anything (ONE question at a time, 2-4 numbered options you wrote for this product, recommended first — they answer with a number and never type a sentence), and the rules: payments only through Boonful checkout (any outside payment link, script or instruction is refused), and everything you make is a DRAFT that only the creator can publish after filling in each section and their payout details. — CONNECT A PRODUCT THE CREATOR ALREADY BUILT AND HOSTS SOMEWHERE ELSE (their own domain, Vercel, Netlify, Cloudflare…). Their code stays where it is; Boonful gets a product page in Boonful's design, a window that opens their live site, visit tracking, their Stripe sales in Business and Sign in with Boonful. Read the project you are in first (name, what it does, prices, the live URL). Pass `url` (the live https address), `name`, `description` (40+ characters, plain words for buyers), `subtitle`, `category`, an `icon` (~256px PNG, base64 or data URI — make one from their logo/favicon if they have one) and `screenshots` [{image, device:'mobile'|'desktop'}] of the real app (mobile 1170x2532, desktop 1600x1000). Saved as a DRAFT. The result gives you: the ONE script line to add to every page of their site (add it yourself, then deploy as the project normally deploys), the Sign in with Boonful snippet (wire it into their existing sign-in so a person inside the Boonful window is signed straight in), whether their site can open inside Boonful and the exact header to fix it if not, and how they connect Stripe. Call it again with the same `url` to update. Never add Boonful payment code: they keep their own checkout.

Check a connected product end to end: is the visit script live on their site (visits arriving), can the site open inside the Boonful window, is Sign in with Boonful verified, is their Stripe connected and syncing. Pass `id` (from studio_connect_product). Use it after you add the script and deploy, and tell the creator in plain words what is done and what is left.

Find people who need what the creator sells, right now, on X, Reddit, LinkedIn, Threads, Bluesky (and Facebook, Instagram, TikTok, YouTube, forums if asked). Write the searches yourself: `x_query` uses X advanced search (people asking for it, e.g. ("looking for" OR "any recommendations" OR "is there an app") ("phrase" OR "phrase") lang:en -filter:retweets), `plain_query` is 1-3 quoted phrases joined with OR for the other platforms. Returns recent posts with their authors; YOU then pick the likely buyers and write a warm first message for each. Nothing is posted or sent for the creator. A few free searches, then Boonful Max.

READ THIS FIRST for anything about social posts. Returns the Scheduler rulebook: what you may do, how to check connected accounts and limits, and how to schedule. The scheduling tools refuse to run until you have called this.

Takes no parameters.

LIVE state of the creator's Scheduler: which platforms Boonful supports right now, which accounts they have connected, posts left today / this month per platform, character limits, and what each platform needs. Call before writing, and again with `when` to check another day.

Put ONE text post in the creator's Scheduler queue for the given moment, on one or more CONNECTED platforms. Confirm the exact text and time with the creator first. The server enforces platform limits, the monthly X share, character limits and the no-outside-payments rule.

The creator's queue and recent posts (id, time, status, platforms, text).

Takes no parameters.

Remove one queued post by id (only posts that have not gone out yet).