Available Tools

List the sites in this Webforgia workspace, newest first. Returns each project's id, name, kind and slug. Use the id with get_project, edit_site or publish_site.

Fetch one project's full Site Spec — the validated JSON that describes every page, section and theme value. Use this before editing so you know what is actually there.

• projectId (required) — From list_projects.

List the built-in expert skills that can be applied to an existing site (redesign, accessibility, SEO, add pricing, translate, and so on). Each entry says what it changes and what it leaves alone. Pass a skill id to edit_site.

How much build allowance this workspace has left. Check it before a long run of builds — a build fails cleanly when the workspace is out, but knowing first is cheaper.

Build a new site from a description and save it to the workspace. Runs the full generation pipeline (plan, generate, audit, repair, photography) and consumes one build credit. Returns the project id and an editor URL. Describe the business, who it is for, and what the page should get someone to do.

• prompt (required) — What to build. The more specific, the fewer rounds of editing.
• buildType — one of website, design, slides, document, dataviz — Defaults to website.
• mode — one of lite, economy, power — How many passes to run. Defaults to economy. Power adds a visual review loop and costs more.
• name — Project name. Defaults to the business name the model picks.

Publish a project's current state to a live URL with every page rendered. Safe to call repeatedly — each publish records a new immutable version. Does not consume a build credit.

• projectId (required) — From list_projects.

Check a Site Spec against the schema without saving or building anything. Free, instant, and the fastest way to find out why an edit was rejected. Returns either valid:true or the exact field paths that failed.

• spec (required) — A full Site Spec object.