Beste

Creates an empty page. The navbar and footer of an existing page are reused by default, so the new page is not headless. A first build stops at three pages; a later session has no limit.

create_page

Adds a product to the catalog. Starts as a draft unless status is set, so nothing appears on the live site by accident.

create_product

Creates a new empty site owned by this account: one blank home page, default theme, no sections, and opens its live preview next to the chat in clients that show MCP Apps. When the person asks for a site, that is the go-ahead: call it straight away, without asking again or offering choices first.

create_website

Deletes a blog post: the page, its sections and the article itself, out of the database. Nothing else on the site holds a copy, so this is not recoverable from the draft. It refuses on the first call and tells you what would be lost; the second call has to carry the post's own slug in `confirm`, and that is for the person to approve, never for you to decide.

delete_post

Deletes a form. Refuses while a section still points at it, unless force is set.

delete_form

Deletes a page and its sections. The home page cannot be deleted.

delete_page

Removes one redirect, so the path answers normally again.

delete_redirect

Removes a section from its page (draft only).

delete_section

Removes a shared component. Refuses while a page still uses it, so the only thing it can delete is something nothing renders.

delete_shared_component

Generates an image with AI and stores it in the site media library. It is refused while any page has no sections: place sections first, then generate, because generating is slow and the preview would sit empty. Spends credits, so only when the person asked for generated images, and never as a question during a build: build with the placeholders and offer images in the hand-over. Reuse list_images when something suitable already exists. Generated images arrive around 2 MB, so before calling, in one message, say what it costs in credits (image_credits) and ask the user whether to optimize them (resize to 1920px, WebP at 80%) and remove the original, and whether to go ahead at that cost; suggest optimizing and removing the original. Call it only after they say yes.

generate_image

What this site can track: which of GA4, Meta Pixel and PostHog are connected, the event names GA4 recommends, and how a funnel is written. Read this before set_link_events — an event sent to a sink the site has not connected fires into nothing, and an invented event name arrives in GA4 with no report built for it.

get_analytics_setup

The entrance animation on every section, and the settings the builder offers. Read this before changing anything: it tells you what the site does now, and it carries the exact type and speed choices to put to the person. Never invent an animation name or a duration; both come from here.

get_animations

One piece with its demo payload: every prop it takes and the value it ships with. Rewrite those values in the customer's words; a piece left on its demo text is as generic as demo copy anywhere else.

get_piece

Where to look at the site: the live URL and the builder URL for the draft. The live URL is the only place the layout can be seen, which get_page_markdown cannot show. There is no public URL for unpublished changes.

preview_url

One product with its variants, options and media.

get_product

How the catalog is set up: the URL prefix product pages live under per language, the default buy button and quote form, currency and price format, sort options, storefront filters, product type links and catalog translations, plus the terms the catalog actually uses. Read it before changing any of these.

get_product_settings

The stored content and style of one section, for the given language. Read this before update_section so a patch does not fight what is already there.

get_section

The starting payload of a section type: { style, content }. content is NOT language-keyed here; add_section wraps it per language.

get_section_defaults

The allowed shape of a section payload: fields, types, enums and which ones are required. Ask for this when a write was rejected or when writing content by hand.

get_section_schema

Summary of one website: theme (with its colour, radius and shadow tokens when the theme is custom), fonts, favicon, languages, the site look and its pages. Does not return section content — use list_pages and get_section for that.

get_site

Every string on a page that should be translated, with an id for each. You translate them yourself and send them back with apply_translation. Fields the renderer switches on (link types, variants) and URLs are left out, so you cannot break the page by translating a token.

get_translatable_text

Marks two or more posts as the same article in different languages. The live site turns the group into hreflang alternates and the language switcher jumps between them instead of re-prefixing the URL.

link_post_translations

Blog posts on the site, with their status, summary, meta description, tags, cover image and table-of-contents flag. Posts are pages with post metadata, and drafts never reach the live site.

list_posts

The typefaces a site can be set in: the catalogue by category (sans-serif for body, serif for headings, monospace for code), the curated pairings set_fonts takes by id, and, with a websiteId, the families that site added itself.

list_fonts

Forms defined on the site, with their ids and every field's name, label, type, placeholder and whether it is required. Form sections reference a form by id rather than carrying fields of their own.

list_forms

The site's media library, newest first: addresses and what each file is. Every row already carries everything known about its file, and a library runs to hundreds. Reuse one of these before generating a new image.

list_images

Languages a Beste site can be built in, exactly the list the dashboard offers. Show the user a handful and let them name any other from this list.

list_languages

Every link on the site, with the tracking each one already carries. This is how you see the whole picture before building a funnel: what pages exist, what leads where, and which clicks are already measured. Each link comes back with a `path` that addresses it exactly; pass that path to set_link_events.

list_links

The looks: each studio set as one site-wide setting. A look is the type scale, the button style, the badge look, card borders and motion, written to the site with apply_look so every section, from any set, arrives dressed the same. Color is the theme's, chosen separately.

list_looks

Pages of a website with the section list of each page (ids, types, order). Pass a slug to get a single page.

list_pages

Products in the site catalog, newest first. Prices come from the first variant.

list_products

The site's redirects: where each one sends a visitor, and whether it is permanent.

list_redirects

Themes set_theme accepts, each with its character read off its own colors (monochrome, blue accent, light or dark). Pick the one that suits the brief yourself; do not offer them as a choice unless the person asks to choose colors.

list_themes

Lists the websites this token can edit, and names the account it belongs to. Always call this first: every other tool needs a websiteId, and the person watching needs to know whose sites these are.

list_websites

Moves a section to another position on its page (0 is the top).

move_section

Opens a live preview of the site's draft next to the chat, in clients that show MCP Apps. It follows every change as it is saved. Call it before the first change to an existing site, every time, so the person watches the edit land; a new site needs no call, create_website opens it. Once per conversation per site. Without a websiteId it asks the person which site to show.

open_preview

Optimizes the large library images a site's pages use, in bulk: each becomes a 1920px WebP at 80% (the dashboard's Optimize for SEO), and every section on those pages is repointed to the optimized copy. Images under 500 KB and already optimized copies are left alone. Ask the user whether to remove the original images before calling; suggest removing them. Run with dryRun first to show what would change.

optimize_images

Puts the draft on the live site, where the public sees it. Everything else writes to the draft only. This is the person's decision and never yours: on an existing site it needs `asked`, quoting what they said when they asked for it. Finished work is not a reason to publish. Looking right is not a reason to publish. Being sure they would want it is not a reason to publish. The one reason is that they said so.

publish

Everything a page says, as text: every section in order with its id and its copy. This is how you check your own work before publishing, and how you find the section you want to edit.

get_page_markdown

Removes a language and deletes its content everywhere: sections, navbar and footer, page SEO, per-language URLs and catalog terms. Critical and not undoable with undo_batch. Removing the default language needs newDefaultLanguage, which only the user may choose: if they have not named it, ask them, never pick one. Two steps: call without confirm to get the impact and a confirmation code, tell the user, and call again with confirm set to that code only after they agree.

remove_language