Pages & Sites

Tools in the pages scope, callable over space-mcp (tools/call) or space-api (REST) with a wks_live_* key that grants pages.

cancel_booking

Scope: pages:write

Cancel a booked appointment (status → cancelled). Get the booking_id from list_bookings. The linked calendar event is kept unless delete_calendar_event:true. The guest is NOT auto-notified — tell them if they should know.

create_blog_collection

Scope: pages:write

Create a blog (collection) — the REAL blog system, not a static page. To make it part of a website, pass site_id from create_site/list_sites. A blog holds the post layout (template_html with {{title}}/{{cover_image}}/{{excerpt}}/{{body}}/{{author}}/{{date}} tokens; a neutral default is used if omitted). Idempotent by base_slug per space. Then add posts with create_blog_post.

create_blog_post

Scope: pages:write

Write a blog post into a collection. Provide body_html (HTML rendered into the blog template), plus optional excerpt, cover_image_url, and author. Defaults to a draft; pass status:'published' to publish immediately (live at /post/<id>). Requires create_blog_collection first.

create_booking_page

Scope: pages:write

Create a real Space booking page so visitors can schedule time. Returns { booking_page_id, slug }. Embed with <div data-wakato-booking="<booking_page_id>"> or link a CTA to /b/<slug>. Active immediately with default Mon–Fri 9–5 availability. Set meeting_location_type to "wakato_meet" so EVERY booking automatically creates a Wakato Meet video-call link.

create_page

Scope: pages:write

Create a new AI-designed web page. EVERY page is part of exactly one artifact — decide FIRST: (a) part of a browseable WEBSITE → create_site kind:"website" and pass site_id; (b) a step of a LANDING flow/funnel → create_site kind:"landing" and pass site_id (steps link FORWARD only, no nav); (c) a single standalone LANDING PAGE → no site_id (pass standalone:true if it's your 2nd+ within the hour). Pass layout_html (a complete HTML document) to build it in one call. Any <form> must use the binding <form data-wakato-form-id=\"<id>\"> and any calendar must use <div data-wakato-booking=\"<id>\"> (or a /b/<slug> link) referencing a real Space form/booking page — create those first with create_form/create_booking_page. Storefront sections: embed <div data-wakato-products></div> (live grid of every product listed on this space, optional data-limit="N") or <div data-wakato-product=\"<product_id>\"></div> (one product's card) — leave the container EMPTY; the platform fills live price/photos/stock with working Buy buttons at render time. Products must be listed on this space first (commerce scope: set_product_listing). Blog section: <div data-wakato-blog-index data-base=\"blog\"></div> fills with published post cards. Link sibling pages with /pg/<their slug> hrefs. Idempotent by title: a same-title page is filled if empty, otherwise returned untouched. ENFORCED: a 2nd+ standalone page within the hour is rejected unless standalone:true — scattering one website/funnel across loose pages is never allowed.\n\nPAGE_DESIGN_BRIEF

create_site

Scope: pages:write

Create a web artifact and DECLARE what it is. kind:"website" = a browseable multi-page site (visitors roam freely via shared navigation). kind:"landing" = a landing page flow: forward-only steps toward ONE goal — opt-in → sales → thank-you etc. — with navigation disabled (when someone asks for a 'funnel', this is it; a single conversion page needs NO site — just create_page standalone). REQUIRED before any multi-page build: create the artifact FIRST, then pass its id as site_id on every create_page call (do NOT scatter pages standalone). Idempotent by title. The first page attached becomes the home page / step 1.

delete_booking_page

Scope: pages:write

PERMANENTLY delete a booking page (its booking history is deleted with it). Refused while upcoming confirmed bookings exist — cancel those first with cancel_booking. Prefer update_booking_page status:"paused" to just stop new bookings.

delete_page

Scope: pages:write

PERMANENTLY delete one page (a published page goes offline). To remove a WHOLE website or landing flow use delete_site instead — it removes the artifact and all its pages in one call. If the deleted page belonged to a site, run validate_site afterwards and fix any nav item that pointed at it.

delete_site

Scope: pages:write

PERMANENTLY delete a web artifact — the WHOLE website or landing flow: by default every page/step is deleted with it (published pages go offline). This is the correct way to remove a website or funnel; deleting its pages one by one leaves the shell behind. Pass keep_pages: true only if the pages should survive as standalone single landing pages (they lose the shared nav/flow).

get_booking_page

Scope: pages:read

Get a Space booking page including its availability and timezone.

get_page

Scope: pages:read

Get a single page including its layout_html (the full HTML document).

list_blog_collections

Scope: pages:read

List the space's blogs (collections). Each blog groups posts and may be attached to a site (site_id). Call before create_blog_collection to reuse an existing blog.

list_blog_posts

Scope: pages:read

List blog posts in the space. Optional collection_id, status (draft|published), limit.

list_booking_pages

Scope: pages:read

List Space booking pages (id, name, slug, status). Reuse an existing one before creating a new one.

list_bookings

Scope: pages:read

List actual booked appointments (guest name/email, start/end, status, attendee_status = whether the guest accepted/declined the calendar invite) across the space or one booking page. Use upcoming_only:true for the forward schedule, search to find a specific guest, status:"cancelled" for cancellations. Answers in the guest's attached form (if any) are in form_data.

list_pages

Scope: pages:read

List pages in the space.

list_sites

Scope: pages:read

List the space's web artifacts (sites). Each is EITHER kind:"website" (browseable multi-page site, shared brand + platform-injected navigation) OR kind:"landing" (a landing page flow — forward-only ordered steps toward one goal, no nav; 2+ steps = a funnel). Returns id, title, slug, kind, status, root_page_id. Call this before create_site to avoid duplicates.

present_page

Scope: pages:read

Show a Space Page live in the user's Space Computer panel (Apps & Pages tab). Call it when you start building or changing a page, or when the user asks to open/see one. Whiteboards and documents cannot be presented. UI-only signal — succeeds even if the panel is closed, and stores nothing.

preview_booking_page

Scope: pages:read

TEST a booking page the way a guest would: returns its full config, the attached form's questions (if any), and REAL bookable time slots computed with the same engine as the public /b/<slug> widget — plus a ready verdict and issues list. Each slot's label is complete — weekday, date, and time already rendered in the requested timezone (e.g. "Tuesday, July 14 at 10:30 AM"; quote verbatim — never pair a time with your own weekday/date or do timezone math) — plus an absolute start_at/end_at (UTC ISO). Use this right after create/update_booking_page to confirm it actually works. Pass a specific date (YYYY-MM-DD) to probe one day, or omit it to scan the next days (default 14) for the first open day.

preview_page

Scope: pages:run

SEE the live page: renders a PUBLISHED page headlessly, captures full-page screenshots (desktop 1440px + mobile 390px), saves them to Space Assets, and runs a vision QA critique (billed to the space wallet) reporting real visual problems — overlapping/clipped content, unreadable contrast, broken images, unstyled sections, empty product/blog containers, mobile overflow. THE QUALITY LOOP for website builds: publish_page → preview_page → fix every severity=error issue → republish → preview again until verdict is looks_good. Combine with validate_site (structure) for a complete check. Requires the page to be published first.

publish_blog_post

Scope: pages:run

Publish a blog post (live at /post/<id>), or pass publish:false to move it back to draft. Requires pages:run.

publish_page

Scope: pages:run

Publish a page so it's live at /pg/<published_slug>. Pass publish:false to unpublish. Requires pages:run. The result includes an automatic link lint (link_issues): severity=error entries are DEAD links/embeds visitors will hit — fix and republish, never leave them. Publishing is step 1 of the quality loop; ALWAYS follow with preview_page.

reorder_site_pages

Scope: pages:write

Set the display order of a site's pages (the order they appear in the site's page list and default navigation). Pass the site's page ids in the desired order; omitted pages sort after the listed ones.

reschedule_booking

Scope: pages:write

Move a confirmed booking to a new slot. Pass new_date (YYYY-MM-DD) + new_start (HH:MM) in the booking page's OWN timezone — find open slots with preview_booking_page first. The new slot is validated against real availability (the booking never conflicts with itself) and the linked calendar event moves with it. The guest is NOT auto-notified.

update_blog_collection

Scope: pages:write

Edit a blog (collection): rename it, replace template_html to re-theme the post layout (keep the six tokens), or attach/detach a site_id / index_page_id (pass null to detach). The base_slug is fixed at creation.

update_blog_post

Scope: pages:write

Edit a blog post's title, excerpt, cover_image_url, body_html, or author.

update_booking_page

Scope: pages:write

Edit an existing booking page. Pass booking_page_id + only the fields to change. Set meeting_location_type to "wakato_meet" so every booking auto-creates a Wakato Meet video-call link.

update_page

Scope: pages:write

Update a page's title/description and/or rewrite its layout_html. Embedded form/booking/product references are re-validated against this space. Storefront containers (data-wakato-products / data-wakato-product="<id>") and the blog index (data-wakato-blog-index) are supported the same as create_page. If the page is already published the change goes LIVE immediately — run preview_page afterwards.\n\nPAGE_DESIGN_BRIEF

update_site

Scope: pages:write

Update a web artifact after creation: title, description, nav_layout (top/sidebar/none), logo_url, root_page_id (the home page / step 1), and the managed nav_config. nav_config replaces the whole nav when provided: { enabled, items: [{label?, page_id? | url?}], cta: {label, page_id? | url?}, style: {sticky?, theme? (auto/light/dark), transparent_on_hero?, logo_position? (left/center), accent_color?} }. Page items must be pages of THIS site; item labels default to the live page title. WEBSITES ONLY for nav: landing pages are forward-only and any attempt to enable a nav on kind:landing is rejected — if visitors should browse freely, build a website instead.

validate_site

Scope: pages:read

Readiness lint for a site BEFORE (or after) publishing: reports dead links (/pg/, /f/, /b/, /pay/, /post/ that resolve to nothing), nav items pointing at deleted or draft pages, form/booking/product embeds that don't exist in this space, and unpublished pages. Run this after building a multi-page site and FIX every error it reports — a site with dead links is not done. Returns { ok, pages_total, pages_published, issues: [{severity, code, message, page_id?, detail?}] }.