Selecting the correct website, page, and language

Documentation / Agentic editing and connections

A connection address identifies the Beeboo service, not the content to edit. A workspace can contain several websites, and a page can have several language variants. Confirm all three targets before approving a write.

Establish the website

Ask the assistant to run list_sites and report the intended site's domain. Use the domain returned by the service as the site value. Do not substitute the hosted MCP hostname, the authorization hostname, or a remembered display name. If the expected website is missing, check account membership and the connected workspace.

Find the page

Use list_pages for ordinary page discovery. Use list_roots when navigation membership, collection ownership, missing references, or translations are relevant. Its inventory includes stored pages that are absent from navigation.

Have the assistant read the complete page with get_page or resolve its exact route with get_page_by_path. Titles and slugs can change; the page ID is the stable identity. Confirm the current path, root, availability, design mode, and any template before preparing an update.

Name the language explicitly

Translations share the source page ID and occupy separate language variants. Include the requested lang when reading and updating a translated page. Do not create a second unrelated page simply because its translated title is different. Ask the assistant to leave other variants untouched unless translation is part of the approved scope.

A safe request is: “Read the French variant of this page on the selected website. Report its ID and current version. Propose a revised introduction without saving.”

After an approved update, read the same variant back and open its public route. If the wrong content appears, check locale routing and fallback before retrying. See languages and translations.