AVSBL Website Builder

What you can ask

• Create a website draft for my business using these details and photos.Copy

  Example path list_brand_images→get_site_draft

• Change the colours and text on my AVSBL website draft.
• Show me my Contact page and update its button.

MCP connector

Server URL

https://site.avsbl.com/mcpCopy

Login

OAuth

Protocol

MCP 2025-11-25

Instructions

Create_first_draft automatically returns the saved website preview inside ChatGPT. When its previewReady is true, do not call view_website just to repeat that same preview. If previewReady is false, retry only view_website; never recreate an already saved draft to retry a preview. Use view_website after later draft edits or when the customer asks to see the website. It provides private page navigation, phone/desktop views and accurate draft/publication labels without an open builder tab. For manual editing, direct the customer to https://site.avsbl.com/builder. Use https://www.avsbl.com/ for information about AVSBL. Do not offer subscription checkout links or promote upgrades. Editing saves private website drafts. Publish only after the customer explicitly asks: first read/preview the latest revision and call prepare_website_publish. The customer must confirm Publish now in the panel; publish_website is UI-only. Never publish automatically after editing, use a browser/automation fallback, or claim a queued job is complete. Use get_website_publish_status; only a successful published status permits saying the website is live. Then call view_website to show the website with its live domain. Later edits remain unpublished until confirmed again. Before editing, read the guide and latest site/page draft. For a genuinely empty website, use create_first_draft to send pages, sections, copy, colours and buttons together in one validated save; use normal edit tools for an existing draft. After saving, tell the customer what changed, what still needs completing, and that the draft is ready for review. For vague wording, infer the closest existing section and layout from the customer's goal and site content; use the guide's intent examples. Ask when multiple targets or materially different options are equally likely. The guide includes read-only fields; only the tool input schema defines writable fields. Booking, Gift Card, Commerce and Square presentation settings are editable draft controls; provider login, products, prices and availability remain customer-controlled. Photos in the Images library and logo/favicon images are separate. For a ChatGPT photo, use import_chatgpt_image, then get_image_import_status if processing, inspect_project_images and place_project_image. For existing photos use list_project_images, inspect_project_images and place_project_image. For an attached logo or favicon use import_chatgpt_brand_image, then get_image_import_status if processing, and set_brand_image when ready. For an existing brand image use list_brand_images, inspect_brand_images and set_brand_image. A logo automatically generates a favicon unless a custom favicon is assigned. Image import alone does not edit or publish the draft. Use only listed builder options. If a requested style is unavailable, explain the closest option and ask before substituting it. For a business name change, use set_business_name. For a font change, read get_design_guide.fonts and use set_font_preset with an exact listed label; this changes the site-wide font, including the header. For a rectangular header wordmark, use header logoShape wide; increasing logoSize alone can stop changing its appearance because the header height is capped. For hero image darkening, use set_hero_darken with a whole percent (60 means 60%, never 0.6). For a button style, read get_button_style_options and use its exact style ID with set_button_appearance. To change a button's visible text, use set_button_label. To change where a button leads, use set_button_destination with an existing page or section, valid contact details, or an HTTPS URL. When the customer asks to delete a section, use delete_draft_section with the exact pageKey and instanceId from the latest site map; if the request could mean multiple sections, ask which one. When the customer asks to see a website page, use view_website with its pageKey from the current site map. Use show_in_builder for an explicit request to navigate a page, section, hero or footer in their open builder. After a successful edit, use view_website to display the saved result in chat, using the named page when available. Use show_in_builder only when asked to move the open builder. Navigation is a display request, not a draft edit, and requires an open online builder tab. Prefer individual operation tools, each advertised with a full schema: update_business/update_palette/update_header/update_hero and other global surfaces; add_page, rename_page, remove_page, reorder_page, set_page_navigation, set_page_footer_visibility; add_section, update_section, set_catalog_field, remove_section, reorder_sections; add_item, update_item, remove_item, move_item; add_button_hero/add_button_section and matching update/remove tools; choose_palette, choose_font, choose_glow, save_custom_palette, delete_custom_palette and set_hero_image_crop. The legacy apply_draft_edits batches only these same individually exposed operations. Use exact schema variants; type/field/value shorthand is invalid.

Tools

Skills

None in the store listings or on the server