AgentBuild

Create a new website with hosting infrastructure. Returns the site slug that all subsequent tools take as their domain parameter. site_build is the one-call alternative that also adds content, applies a theme, and deploys a preview.

site_create

Creates one typed content item, such as a page or blog post, on the preview lane. `section_types` provides the accepted field shapes for page sections. A minimal page: { type: "page", slug: "home", data: { title: "Home", sections: [{ type: "hero", variant: "centered", content: { heading: "Welcome" } }] } }. A new page is reachable at its URL but is not automatically added to primary navigation; `site_settings_update` manages authored `nav_items`. Legal pages can use `data.nav_placement: "footer"` for fallback footer navigation, and `data.noindex: true` keeps a page (a thank-you or paid landing page) out of search engines and the sitemap. Blog posts require the blog feature enabled through `feature_set`. Public content reflects supplied business facts. Unknown factual material remains a clearly marked placeholder tracked through `discovery_update`. The live custom domain changes only after `site_publish`.

content_create

Permanently delete a site and all its resources. This cannot be undone. Only use when explicitly asked.

site_delete

Delete a content item permanently.

content_delete

Deletes an uploaded asset from the site's library by ID from `asset_list`, freeing its quota slot. It refuses with `asset_in_use` while a section still references the asset; remove those references with `content_update`, then retry. The underlying file is retained so previously published versions keep rendering.

asset_delete

Updates one content item and refreshes the preview site in a single 30-45 second operation. The live custom domain remains on its last published version until `site_publish`. Exactly one update mode applies. `section` changes one section in place by its `section_id` from `content_get`, the safe single-section edit that avoids re-sending the page. `data` replaces the complete stored data object. `patch` recursively merges objects, but arrays replace wholesale; a patched `sections` array therefore replaces the entire stored `sections` array and carries `expected_revision` from the read it was built from. A replacement dropping stored sections lists the dropped ids in `confirm_section_removals` after the human's go-ahead. The content ID comes from `content_list` or `content_get`. A brief progress update before the call accounts for the build wait. For several related edits, the efficient cadence is multiple `content_update` writes followed by one `site_deploy`; this compound operation fits a single final edit. In-flight builds may be coalesced with status guidance.

update_and_deploy

Creates the draft site, applies its theme, stores pages, brief, and DiscoveryChecklist, and deploys the preview at `{slug}.agentbuild.site`. `site_publish` publishes the current stored content to the live domain later. The structural-draft gate requires the human's business name and type, a human-confirmed preset, page structure, at least three answered discovery items, and substantive `discovery_notes`. Fewer than three answers returns `DISCOVERY_INCOMPLETE`; notes under 20 characters return `BUILD_VALIDATION_FAILED`. Unknown business facts are represented as tracked placeholders rather than invented content, and section copy uses the public business voice. Answered brand facts auto-apply: hexadecimal brand colors from discovery become theme overrides, and a supplied logo is installed when discovery identifies one. The response reports what applied, while `site_status.unapplied_discovery` identifies remaining gaps. Empty template content is scaffolded and tracked as placeholder. `section_types` supplies section shapes and `image_library` supplies candidate photos. `nav_items` seeds an authored primary navigation; the fallback derives navigation from pages, with the logo linking home. If only the deploy leg fails, `site_deploy` resumes it; a partial build names each failed write's recovery tool. Another `site_build` for the same slug enters update mode: matching pages are replaced, the theme is reset from the preset, only supplied navigation fields are overwritten, and the preview is redeployed.

site_build

Fetch the human's account profile: email, plan, and saved contact fields (first_name, last_name, phone, city, country, etc.). Use this to inspect which profile fields are already saved — typically before calling account_update_contact so you only ask the human for fields that are still missing. Street address returns only as `address_on_file`. (Contact details are stored on the account profile for support and any future registrar features; AgentBuild does not register domains in-connector — the human buys a domain at any registrar and connects it with domain_add_custom.) Returns structured data in `structuredContent.account`.

account_get

Get form submissions for a site — submission data, timestamps, and read status. While no notification destination is configured (site_status email.notify_to), submissions land in storage only — no email is sent. Wire delivery anytime with email_setup; it applies to new submissions going forward (old ones are not replayed). Returns structured data in `structuredContent.submissions`: { items, total, has_notification_configured (boolean — whether delivery is wired; the human's email address is not exposed here), truncated (true when more than the 500 most-recent submissions exist), _warning }.

form_submissions

Reads the site's persisted theme configuration, including preset, colors, typography, and style tokens. A site without an established theme returns null; `site_build` establishes the initial theme. The persisted result supports design descriptions and informed `theme_set` changes, while `update_and_deploy` leaves theme state unchanged. Theme metadata is design context rather than public section copy. Returns the full ThemeConfig or null in `structuredContent.theme`.

theme_get

Returns first-party, cookieless site analytics for questions about traffic, leads, and performance: pageviews, leads, top pages, top referrers, top countries, device breakdown, and raw current-versus-previous-period counts. Full results appear in `structuredContent.analytics`, and the text body is a brief relay-safe summary. Leads and conversions are the primary small-business outcome, with traffic as supporting context. Counts describe observations rather than proving that a site change caused them; plausible context can include seasonality, ad spend, or search indexing. Neutral summaries and optional follow-ups avoid attributing wins to the agent. `unique_visitors` is approximate because it uses same-day grouping without persistent visitor IDs. `has_data=false` means no traffic is recorded for the period, and `site_status` provides site-health context when that is unexpected. Chart output is unavailable. Supported periods are `7d`, `30d`, `90d`, `month_to_date`, and `last_month`, with `30d` as the default. Related reads include `form_submissions`, `tracking_add`, and `site_status`.

site_analytics_summary

Get full details of a specific content item by ID. Use this to read a page's sections, a blog post's body, or any content item. More efficient than content_list when you already have the ID. Returns structured data in `structuredContent.content`: { id, type, slug, data, created_at, updated_at }.

content_get

Reads the site's current navigation, footer, and logo settings. A null result means no explicit chrome settings exist and template defaults will render. `site_build` can seed these settings, and `site_settings_update` handles later free-form edits. Chrome state is separate from `theme_get` design tokens and `content_get` page content. Returns SiteChromeSettings or null in `structuredContent.settings`.

site_settings_get

Returns full site state for orientation and preflight: deployment, theme, features, navigation, `launch_checklist`, and `page_summaries`. `page_summaries` lists each page's slug, title, section types, and variants, providing structural context without separate content reads. Navigation state includes `source=authored|fallback|floor` and `cta_mode=explicit|auto|off`; `auto` promotes a contact or booking target when one exists. Two-lane fields distinguish the always-present `preview_url` from `live_url`, which is null until a custom domain is attached. `preview_is_ahead_of_live` reports unpublished preview changes, and `domain_required_for_publish` reports the custom-domain precondition. `launch_checklist` covers `page_titles`, `meta_descriptions`, `og_tags`, `favicon`, `image_alt_text`, `heading_hierarchy`, `json_ld`, and `llms_txt`. `recent_deployments` contains the five latest main-branch versions with `{ version, status, deployed_at, rollback_targetable }`; `rollback_targetable` identifies versions accepted by `site_rollback`. The top-level `url` is a deprecated alias for `live_url`, falling back to `preview_url`.

site_status

Reads either the supported schema.org catalog or stored structured-data configuration. With no arguments, it returns recognized types and property allowlists. With `domain`, it returns the site-level Organization or LocalBusiness entity. With `domain` and `page`, it returns page-level configuration. `inferred: true` means no explicit configuration is stored and the platform will infer defaults at `site_build`, including a LocalBusiness subtype from category, Organization when no address exists, BlogPosting for blog posts, and FAQPage for pages with FAQ sections. `schema_preview` shows the rendered stored shape, and `schema_set` stores refinements based on known business facts. Read-only.

schema_get

Reads the account's subscription state: { plan, status, trial_ends_at, current_period_end, cancel_at_period_end, has_payment_method, complimentary }. Every connected account is on an active paid, trialing, or complimentary plan; `complimentary: true` means full access without a subscription to manage or renew. Status reflects Stripe states such as `trialing`, `active`, `past_due`, and `canceled`. Billing context applies to direct account questions such as subscription status or trial timing. This surface is read-only and provides neither in-connector checkout nor account changes. Returns `structuredContent.billing`.

billing_status

Returns a template's structural recipe: pages, section order, variants, navigation and footer chrome, and collection shape. Templates contain scaffolding rather than business content: section `content` objects are empty, collection `items` arrays are empty, and `content_mode` is `structural`. Empty sections are automatically marked placeholder on the DiscoveryChecklist. The `pages` array is the direct `site_build` input and preserves recipe structure when passed unchanged. `section_types` provides canonical field shapes and variants, while `theme_presets` provides the visual layer. The included `preview_url` is the human-viewable template preview. Returns `structuredContent.template`: { id, name, ..., content_mode, preview_url, pages, chrome, features, business_info, collections }.

template_get

Read the analytics, conversion-tracking, and SEO-verification providers currently configured on the site. Returns the configured array (each entry: provider type + its IDs) plus `available_providers` — the Tier 1 catalog showing required fields and format examples per provider. Empty `tracking` array on a new site is normal; the agent can offer the catalog to the human if asked. Read-only. Returns structured data in `structuredContent.tracking`: { tracking, available_providers, max_providers }.

tracking_list

List all section types, variants, and their props. Call this when you need to know what sections are available for building pages. Returns the complete component vocabulary.

section_types

List all DNS records for a site's custom domain. Use to inspect or debug DNS configuration. Returns structured data in `structuredContent.dns`: { records, total } (or { records: [], message } when no custom domain attached).

dns_list

Reads recent consent artifacts for going-live publishes and takedowns, Google Workspace email setup, and support escalations. It supports authorization-history questions and follow-up session context, including whether a similar action was previously approved. Custom-domain attachment is not a consent artifact; `domain_list` and `site_status` provide that history. Artifacts are ordered newest-first and include `action_type`, the human's verbatim authorization, confirmed-action details, risk class, and timestamp. Results appear in `structuredContent.consents`: { items, total }. Historical artifacts do not satisfy a fresh `consent_required` response. Consequential tools still capture current human approval when required. This read-only tool neither creates nor bypasses consent.

consent_history

List content items for a site — summary mode by default. Each item carries id + type + slug + a small per-type `summary` (page → title + section_count + section_types[]; business-info → name + category; blog-post → title + excerpt; etc). Use this to find content IDs for updates without paying the cost of the full `data` blob (which can be 5-10 KB per page when sections are populated). Returns structured data in `structuredContent.content`: { items, total }. If you need the FULL data (e.g. to read a page's section content before update_and_deploy), pass `verbose: true` — that returns the same items with the complete `data` field populated. Or, if you already have the ID, use content_get instead — it's the targeted form and never returns more than the one item you asked for. Filter by `type` to scope the list (page, blog-post, menu-item, product, business-info, team-member, testimonial, faq).

content_list

List all sites in the account. Use this to see what sites exist, check their status, or find a site slug. Returns structured data in `structuredContent.sites`: { items, total, account }.

site_list

Lists available site templates with { id, name, description, category, preset, page_count, preview_url }. Each template supplies a complete structure for customization and a live demo site at {id}.agentbuild.site; the lookbook is at templates.agentbuild.it/templates. Returns the cards in `structuredContent.templates`.

template_list

Lists available theme presets with their colors, fonts, descriptions, per-preset preview links, and the gallery URL at templates.agentbuild.it/themes. The human-viewable previews provide a visual basis for selection before `theme_set`. Also returns `palette_vocab`, the `palette_seed` hue and mood words. Returns preset cards in `structuredContent.presets`.

theme_presets

List all uploaded assets (images, files) for a site with their URLs. Returns structured data in `structuredContent.assets`: { items, total, storage }.

asset_list

List the domains the human has on AgentBuild: BYOD domains connected via domain_add_custom (parent zones and subdomains; legacy rows may show registrar 'namecom'). Use it when the human asks what domains they have, when checking whether a custom domain already exists before site_publish, or before coaching them to connect another. Each row carries domain, registrar ('namecom' or 'external'), status, registered_at (the connect date here, not the registrar's), expires_at, auto_renew, whois_privacy, and attached_to_site (the sites currently using the domain at apex or any subdomain; empty array when no site is attached). auto_renew / whois_privacy are null on every row — AgentBuild holds no live registrar relationship, so they are unknown here, not off. Renewal and privacy questions go to the registrar the human bought the name from. To check if a name is available, use domain_check. Returns an empty list (not an error) when the human owns no domains yet; next_actions guide toward domain_check / domain_add_custom.

domain_list

Opens an interactive photo panel in the chat where the human picks image options and adds their own photos. Use it to see and pick image options, or to upload when no chat attachment reached asset_upload. Pass images from image_search or image_library to show as options, or omit for upload-only. Returns once the panel opens — the human's choices arrive LATER as a follow-up message or context update. Verify uploads with asset_list when they say they're done; ask which options they picked if a pick didn't come through. A photo reaches the site only after a content change places it. Where the panel can't render, share the returned upload_url.

media_panel

Renders the stored site- or page-level structured-data configuration in the shape emitted by the build pipeline. Platform-managed joins-AggregateRating, Person[], OfferCatalog, Menu, BreadcrumbList, and Event[]-are applied during a build and are absent from this stored-config preview. The result supports review after `site_build` or `schema_set` and before `site_publish`. Read-only. Returns `structuredContent.preview`: { raw, rendered, note }.

schema_preview

Publishes the site's current stored content to the live site at its verified custom domain. The preview site is the review surface and is expected to be current and approved first. Publishing is a reviewed milestone rather than an edit-by-edit step and usually takes 25-35 seconds. The first publish to each custom domain requires the human's verbatim approval in `human_authorization`; later publishes to the same domain reuse that consent artifact. More than three discovery placeholders require the human's approval and `confirm_despite_placeholders: true`. Sites with custom-code sections require disclosure that those sections are best-effort owner code and `confirm_custom_code: true`. After `domain_verify`, TLS may need 2-5 minutes. `tls_provisioning` means only the certificate is outstanding: retry after `retry_after_seconds` with the same arguments — no rebuild; the retry resumes at the certificate check (result field `rebuilt`). First apex publish adds the `www` → apex 301.

site_publish

Removes a configured tracking provider. Removing `gsc_dns` also attempts to delete its TXT verification record; a DNS cleanup failure does not block removal of the tracking configuration. `update_and_deploy` applies script removal to the preview site.

tracking_remove

Restores the live custom domain to a previously published Cloudflare deployment, usually within about 25-35 seconds. The preview site and stored D1 content remain unchanged. Rollback changes the published artifact, not the current content. Later `site_publish` operations rebuild from current stored content, including edits made after the selected version. Restoring the older content itself is a separate `content_update`. A verified custom domain and a targetable deployment are required. `site_status.recent_deployments` lists recent version strings and their `rollback_targetable` state. Versions published before deployment IDs were captured return `rollback_unavailable`; their recovery path is a content correction followed by `site_publish`. A brief progress update before the call identifies the selected version and expected wait.

site_rollback

Captures a static screenshot of the human's own AgentBuild site and returns a base64 image. It is useful after deployment for verifying visual changes; arbitrary external URLs are outside its scope. Cloudflare edge caches may need 10-15 seconds after `site_deploy` or `update_and_deploy`. During that window, `edge_cache_pending` indicates a capture race rather than a failed deployment. A new site's `ssl_provisioning_pending` may need 30-60 seconds. When Browser Rendering is unavailable, the response contains the site URL instead. A screenshot shows only the final painted state, not entrance motion, hover states, or scroll-triggered behavior. `theme_get` and `site_status` report the resolved animation tier. An unexpectedly blank region may also be a capture limitation; `content_get` and `site_status` provide corroborating state before any content-removal decision.

site_screenshot

Finds licensed stock photos and stock images for an AgentBuild site from Pexels, with attribution. The response includes a human-viewable `gallery_url` for picking and returns candidate image objects; a later content update places the selected image. Each candidate includes its URL variants, alt text, dimensions, and attribution. Using the complete selected object preserves responsive image generation, while `section_types` identifies the accepted image field for each section. `image_library` provides curated business-type imagery, and `media_panel` collects the human's own photos.

image_search

Sets the destination for email sent to unmatched addresses on the custom domain. Initial setup is `email_setup(mode="forwarding")`, which also configures notifications. `email_catchall` supports later changes to the existing catch-all destination.

email_catchall

Adds one address-specific forwarding rule on the custom domain, such as [email protected] to [email protected]. Initial setup is `email_setup(mode="forwarding")`, which configures catch-all delivery and notifications. `email_forward` supports additional per-address routes after that setup.

email_forward

Configures email for an attached custom domain in one of three modes. `forwarding` routes received domain mail to `forward_to` (refused with `existing_mail_detected` when the domain already has live MX). `workspace` configures MX, SPF, and DMARC for an existing Google Workspace mailbox; already-live Google MX records the route only, changing no DNS. `external` records that the domain's email already works elsewhere and changes no DNS — it only sets `notify_to`, where contact-form submissions are delivered. Workspace mode requires `workspace_verified: true` only after the human confirms the mailbox is active (premature DNS makes inbound mail bounce), plus their verbatim approval in `human_authorization` (hard-to-undo DNS). Forwarding and external are reversible and skip that gate. The chosen destination delivers contact-form submissions and appears as `site.email.notify_to` in `site_status`. An attached custom domain is a prerequisite; `domain_add_custom` handles a domain the human already owns.

email_setup

Loads the saved business brief, DiscoveryChecklist, and highest-priority pending items at the beginning of a discovery session. With `domain: "new"`, the response lists existing sites or supplies first-site guidance. After a new site is created with `site_create`, the site's slug loads its checklist. With an existing slug, the response resumes saved answers and identifies the next pending topics, avoiding repetition of completed discovery. `theme_presets` supplies current visual-direction choices. Saved discovery state is the source of truth for later `discovery_update` and `site_build` calls.

discovery_start

Takes a site off its custom domain: it stops serving there, the domain detaches, and links and search results pointing at it break. Content, theme, form submissions, uploaded images and the shareable preview site stay, and the human keeps the domain at their registrar. domain_add_custom, then domain_verify, then site_publish puts it back. Each call carries the human's verbatim reply in human_authorization; a call without it returns the consequences to read them first.

site_unpublish

Records a site capability flag: blog, forms, products, bookings, or members. `blog` is the implemented workflow: enable it, create `blog-post` items with `content_create`, add a `blog-list` section, and refresh the preview with `site_deploy`; posts render at `/blog/[slug]`, and disabling stops blog rendering while stored D1 content remains. A page-derived navigation receives an automatic Blog link, while an authored navigation is edited through `site_settings_update`. The remaining flags are stored for upcoming capabilities and do not change rendered behavior yet. `site_status` reports the current feature state.

feature_set