REQUIRED FIRST STEP. Returns the question script you MUST ask the user before calling generate_site. Why: Template Vault's value is integration discovery — the generator detects what each business needs (WhatsApp button, Instagram block, booking, online ordering, etc.) based on these answers. Skipping discovery produces minimal text-only sites and embarrasses the user. ALWAYS call this tool first when a user asks to build/generate a website. After receiving the questions, ask them ONE AT A TIME in conversation — do not dump the whole list. Note answers, then build a complete businessProfile object for generate_site.

List the visual personalities (styles) Template Vault can generate. Use to pick a style that fits the business before calling generate_site.

Generate a new website for a business. Returns a jobId immediately — the build runs asynchronously (~30-90s). Poll get_generation_status to find the site_id + preview URL once it's done.

PREREQUISITE: You MUST have called discover_business_needs first and asked the user the resulting questions. Calling generate_site without a populated businessProfile produces a poor site missing integrations — WhatsApp buttons, Instagram embeds, booking widgets — and that embarrasses both the user and Template Vault.

A populated businessProfile should include AT LEAST: a phone or whatsapp number, hasPhysicalLocation (+ address if true), hasSocialMedia (+ handles if true), and languages. If the user truly refuses discovery, pass { skippedDiscovery: true } so the backend can warn in the admin log.

Content policy: Template Vault declines categories listed at https://www.the-template-vault.com/docs/mcp/content-policy (adult content, hate speech, scams, illegal goods, CSAM, impersonation/phishing). Obvious matches are rejected synchronously with a clear error; subtler cases are caught by the underlying Anthropic model.

Counts against the user's monthly generation quota.

Check the status of a generation job. Returns status (pending|processing|completed|failed), siteId (when completed), and an estimated progressPercent. Recommended polling interval: 5 seconds. The job typically takes 30-90 seconds total.

List sites owned by the authenticated user. Use to find a siteId before calling publish_site.

Publish a site to production at slug.the-template-vault.com. First publish wires up the GitHub repo + Vercel project; subsequent calls just trigger a Vercel rebuild that picks up the latest config from Supabase.