Builderii

Changes an app on the board (get_diagram shows its screens). In "screens" list only the screens that change or are new: a changed screen keeps its id and lists all of its components as they should end up; a new screen gets a new id (give "appName" and "platform" as they are). List the ids of screens to delete in "removeScreens". Screens you leave out stay exactly as they are. linkTo can point at any screen, existing or new; to link an existing screen to a new one, list that screen as changed.

update_app_screens

Whether a job from generate (or another AI tool) is done, and what it did. Waits up to 20 s.

get_ai_job

Leaves a comment, pinned beside the element whose text matches on (else at the top left of the content).

add_comment

A new board, empty or from a template. Returns its id and link.

create_board

Draws a database diagram (ERD): tables with columns, primary and foreign keys — or from SQL CREATE TABLE statements or a Prisma schema in sql.

create_database

Draws a flowchart from steps and arrows, laid out automatically (to the right of what's on the page). Kinds: start, end, process, decision, io, document, database, subprocess, note, actor.

create_flowchart

Draws a mind map from ideas with parents (one central idea with parent ""), laid out automatically.

create_mindmap

Draws a roadmap: lanes, dated items (tasks and milestones) and dependencies, on a timeline.

create_roadmap

Draws a sequence diagram: participants (actor, service, database) and messages in order (sync, async, reply).

create_sequence_diagram

Draws a sitemap: pages in a tree (one home page with parent ""), each with its sections.

create_sitemap

Draws app screens (a clickable prototype: press Play in Builderii) for a phone, tablet, web or desktop app, laid out automatically. Describe each screen as an ordered list of components, top to bottom. Builderii lays them out automatically, so give no coordinates. Fields of a component: - kind: one of the component kinds below. - text: its main visible text (button label, heading, field label, card title, list-item title). "" when it has none. - detail: secondary content, by kind — input/search/textarea: placeholder; select: selected value; card/modal/hero: body text; listItem: subtitle; tabs/tabbar/navbar/list/segmented/sidebar/breadcrumbs/table/pricing/footer: comma-separated items (tabbar: 3–5 short tab names; table: column names; pricing: plan names); icon: a lucide icon name (e.g. "bell"); chart: "bar" or "line". Otherwise "". - row: an integer. Consecutive components with the same row number sit side by side (e.g. two half-width fields, three stat cards, a row of chips). Give every other component its own new number. - size: "sm", "md" or "lg" (relative emphasis for headings, images, cards). - linkTo: the id of the screen this component opens when tapped (buttons, list items, cards, tab bar, links), or "". Link the screens into a sensible, clickable flow — every screen should be reachable and the primary action of each screen should lead somewhere. Kinds: heading, paragraph, label, button (primary), buttonSecondary, link, input, textarea, search, select, checkbox, radio, toggle, slider, progress, segmented, chip, badge, rating, stepper, datePicker, image, avatar, icon, divider, card, listItem, list, table, chart, map, video, modal, toast, tabs, breadcrumbs, pagination, keyboard, container. Mobile only: topbar (title bar with back/menu; text = screen title) first, tabbar last for main sections. Web/desktop only: navbar first (text = brand; detail = nav items), sidebar for app dashboards (detail = sections), hero, pricing and footer for marketing pages. Good screens have 5–12 components, real content (names, numbers, prices, dates) and one clear primary action. Ids are short slugs like "home", "detail".

create_app_screens

Draws Mermaid as native, editable shapes: flowchart / graph (TD, LR…), sequenceDiagram or mindmap.

import_mermaid

Builderii's AI adds new ideas around one: children of a mind map idea, or sticky notes beside a note or shape.

expand_ideas

One board as text (screens, steps and arrows, mind maps, notes, comments), by the id search returned.

fetch

One diagram's structure with short ids (as the update_* tools take them), and how to change it.

get_diagram

Builderii's AI groups sticky notes by theme into titled, coloured columns (all the page's notes, or the ones given).

cluster_stickies

Makes app screens clickable: tapping an element (by its text) on one screen opens another ("back" goes back), and which screen the prototype starts on.

link_screens

The boards the user can open (theirs, shared with them, their teams'), newest first, with links.

list_boards

The diagrams on a page — flowcharts, mind maps, app screens, sequence diagrams, sitemaps, brainstorms, roadmaps, database diagrams — with the ref each update_* tool takes.

list_diagrams

Board templates (flowcharts, mind maps, wireframes, workshops, planning…) create_board can start from.

list_templates

Builderii's own AI does what the board's AI bar does: draws app screens (a clickable prototype), a flowchart, mind map, sequence diagram, sitemap, brainstorm, roadmap or database diagram from a prompt — or changes one already on the page when the prompt is about it (pass diagram to name it). With image_url it turns a screenshot or sketch into app screens (or a flowchart). It runs as a job that puts the result on the board itself; this waits up to 20 s, then returns a jobId for get_ai_job. Counts against the user's monthly AI requests. To draw a structure you've written yourself instead, use the create_* tools.

generate

A board's pages with the diagrams on each (refs to change them), and either a text outline (default) or one page's elements as JSON with ids (format json).

read_board

Builderii's AI rewrites one element's text as instructed (shorter, friendlier, in Spanish…).

rewrite_text

Find Builderii boards whose name or content mentions the query → results with id, title and url (fetch reads one).

search

Builderii's AI summarises a page (or the elements given): title, summary, key points and next steps, also added to the board as a note unless save is false.

summarize_board

Builderii's AI turns an app screen into working HTML and React (Tailwind) code, also placed beside the screen unless save is false.

screen_to_code

Builderii's AI writes a product spec (goals, user stories with acceptance criteria, edge cases, open questions) from a page or the elements given, as Markdown and as a new doc board unless save_as_doc is false.

write_spec