create_project
ChatGPTCreate a new website project. If the user has not created any project yet, the assistant should ask whether to create one. Before creation, the assistant must confirm the project name with the user. This tool does not require UI confirmation. After a successful creation, call get_project_pages again with the returned project id.
create_web_page
ChatGPTCreate a new web page under a specific project in VIXNODE. MANDATORY PRE-CALL CHECKLIST: Before invoking this tool, the assistant MUST have explicit user confirmation for: 1) Target project: say the project name and ask the user to confirm. Even if there is only one project, confirmation is still required. Do not auto-select a project even if the account has exactly one project. The assistant may suggest the only available project, but must wait for user confirmation before calling create_web_page. Do not display project_id or page_id to the user unless the user explicitly asks for those IDs. 2) Style source: ask whether to use A. uploaded image as style reference, B. a VIXNODE reference theme, or C. a custom style. Also tell the user that a style list UI can be shown for interactive style selection. When asking this, explicitly tell the user they can define custom style preferences (for example: color palette, typography, spacing, visual mood, component style, and reference sites). If the user chooses VIXNODE reference theme, call get_reference_themes first. If the user chooses uploaded image/custom style, summarize the interpreted style and ask for confirmation. If the user provides an image and asks to create a page based on it, treat the image as a proposed style source, not as final confirmation. The assistant must summarize the interpreted style and ask whether to proceed with that style. Preview confirmation generated by this tool does NOT replace the above checks. Use mode='preview' to generate preview only. Use mode='create' for actual creation with confirmByUser=true and confirmToken. Input keys (only): project_id, name, page_id, pageType, layout, lang, public, fileName, html, mode, confirmByUser, confirmToken. Legacy key confirm is accepted for backward compatibility only. Do not use removed keys: selected_theme_id, selected_theme_name, themeConfirmed. Note: If the user does not mention programming details, respond in plain language. If the user mentions programming details, then respond with code-related content.
get-image
ChatGPTRetrieves one project image (or thumbnail) for MCP widgets without relying on browser direct /API/GetImage access.
get-photo-gallery
ChatGPTRetrieves uploaded project images and displays a multi-select gallery. Default project_id is empty, and no gallery data is loaded until a project is selected. Before calling this tool with a non-global project_id, ask the user whether to open another project's gallery. After user selection and submit, selected image paths are sent back to the model for webpage content generation. If the user mentions photo gallery/image library, selecting images, or replacing/changing photos, call this tool.
get_account_info
ChatGPTRetrieve information about a VIXNODE account, including email, display name, plan details, and quotas.
get_all_project_pages
ChatGPTRetrieves all pages across all website projects for fast navigation and search. Invoke this MCP tool by name 'get_all_project_pages' directly (do not construct HTTP paths such as /VIXNODE/... ). In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs.
get_project_page_html
ChatGPTRetrieves the HTML design content of a specific page within a project. This is the HTML content of the page that has not been published.
get_project_page_html_by_version
ChatGPTRetrieves project page HTML content by version (commit sha).
get_project_page_html_compare_by_version
ChatGPTCompares a project page HTML version with its previous version and returns patch and both contents. Please provide a plain-language summary of changes first. If the user asks for programming details, then explain using code-focused technical terms.
get_project_page_html_history
ChatGPTRetrieves version history (sha and versionDateTime) of a specific project page HTML. To get the HTML content for a specific version, call the 'get_project_page_html_by_version' tool with the desired version.
get_project_page_seo_setting
ChatGPTRetrieves SEO settings for a specific project page, including SEO meta tags and SEO data structure. When links are provided in the result, always include and present all link fields in your reply (resource_link, published_link, validator_rich_results, markup_helper).
get_project_pages
ChatGPTRetrieves a list of project pages along with their details (such as page name and URL). In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs.
get_published_page_html
ChatGPTRetrieves the published HTML content of a specific page within a project.
get_reference_themes
ChatGPTRetrieves all reference themes. These themes define different categories, types, and color options that can be applied to the appearance and style of the site. When the user asks to change style/theme/look-and-feel/color palette/visual tone (for example: '改變風格', '換主題', '調整配色', 'make it more modern', 'switch to a minimal style'), call this tool first to get candidate themes before proposing or generating modifications.
get_seo_data_structure_sample
ChatGPTRetrieves SEO data structure samples from seo_dataTypes.json. You can optionally provide a specific type value (for example: Article, FAQPage, Product) to return a single sample.
get_url_html
ChatGPTRetrieves HTML content from a URL.
get_website_projects
ChatGPTRetrieves a list of projects associated with the authenticated user's website. In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs.
modify_project_page_seo_setting
ChatGPTModifies SEO settings for a specific project page. This tool can update seo tags (title/description), seo data structure (JSON-LD array), or both in one call. Important process rules: (1) Execute only after the user has explicitly confirmed the final modifications. (2) Before calling this tool, always present the exact modification result to the user for confirmation. (3) If updating seo data structure, call get_seo_data_structure_sample first to get valid sample formats before composing JSON-LD. (4) After successful update, call get_project_page_seo_setting again so the user can review the latest SEO settings and links.
modify_web_page
ChatGPTModify an existing web page under a specific project and publish the latest HTML content. IMPORTANT: Before regenerating the page HTML for any modification, ALWAYS call get_project_page_html first to fetch the latest live HTML of the page. Never generate new HTML from memory or a stale copy; always base your changes on the freshly fetched HTML to avoid overwriting updates made after the last call. Target confirmation rule: if the user does not clearly specify the modification target (for example which project/page/section/content to update), the assistant MUST ask for confirmation first and must not modify proactively. Do not display project_id or page_id to the user unless the user explicitly asks for those IDs. Theme/style rule: only when the user asks to change style, theme, color palette, layout, visual tone, or overall look-and-feel, the assistant MUST first call get_reference_themes or show suitable themes. Modification flow: 1. Call get_project_page_html to read the current HTML. 2. If the modification is about content only, apply changes to the fetched HTML and call this tool for preview/confirmation. 3. If the modification is about style/theme/layout/look-and-feel: show or retrieve reference themes first; wait for the user to select a theme; ask whether to apply the selected theme; only after confirmation, generate HTML aligned to that theme and call this tool. 4. The page is modified only after user confirmation in the UI. Important theme mapping rule: if the user selected a theme id such as Style-16, that theme id is only a reference used to derive the final HTML/CSS. Do not submit theme_id, selected_theme_id, selected_theme_name, or themeConfirmed in the final modify call; the final call must submit the generated html/css through html instead. Input keys (only): project_id, page_id, name, fileName, public, pageType, layout, lang, html, confirm, confirmByUser, confirmToken. Do not use removed keys: selected_theme_id, selected_theme_name, themeConfirmed. Note: If the user does not mention programming details, respond in plain language. If the user mentions programming details, then respond with code-related content.
switch_account
ChatGPTReconnect VIXNODE and choose a different account.
upload_image
ChatGPTUpload one image to the selected project photo library.
