chunk_upload_file
ChatGPTUpload one file to project storage over multiple calls. For a file whose total size is 3 MiB or less, first try the 'upload_file' tool; use this chunk tool for larger files or when the single-call upload cannot be completed. For webpage-related resource files, prefer a private upload with isPublished=false. Only upload a public file when explicitly required and after carefully confirming the target, because the same file path directly overwrites the live resource used by the published website. Split the original file bytes into fixed-size chunks, Base64-encode each chunk independently, and call this tool sequentially from chunk_index 0 through chunk_total - 1 using identical upload_id and file metadata.
chunk_upload_image
ChatGPTFinal chunk commit writes the resource; an existing filename and its thumbnail can be overwritten, and Blob URLs may allow public access. Upload one image to a project photo library over multiple calls. For an image whose total size is 3 MiB or less, first try the 'upload_image' tool; use this chunk tool for larger images or when the single-call upload cannot be completed. Split the original image bytes into fixed-size chunks, Base64-encode each chunk independently, and call this tool sequentially from chunk_index 0 through chunk_total - 1 using identical upload_id and file metadata.
chunk_upload_video
ChatGPTFinal chunk commit writes the resource; an existing filename and its thumbnail can be overwritten, and Blob URLs may allow public access. Upload one video to a project video library over multiple calls. For a video whose total size is 3 MiB or less, first try the 'upload_video' tool; use this chunk tool for larger videos or when the single-call upload cannot be completed. Split the original video bytes into fixed-size chunks, Base64-encode each chunk independently, and call this tool sequentially from chunk_index 0 through chunk_total - 1 using identical upload_id and file metadata.
configure_project_domain
ChatGPTAttach the specified custom domain to a project through the external domain/SSL provider. Revalidates subscription eligibility and DNS before changing the binding. If a domain is already configured, first call with confirm=false to receive the impact, obtain explicit user consent, then call with confirm=true. Reconfiguration removes the old binding before creating the new one; a later failure may leave the old custom URL unavailable. Initial attachment does not require confirm=true. After successful configuration, retry pending status up to twice at 30-second intervals and save retrieved status to the project; stop when ACTIVE_SSL. Status refresh errors do not undo successful configuration and are reported as status_refresh_error. Does not publish pages. SSL may remain pending; use get_project_domain_status afterward.
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_project_page
ChatGPTCreates exactly one new project page without publishing. Follow the VIXNODE Website Builder Skill's planning and layout workflow before calling this exceptional no-preview tool. NEVER use this tool for an initial or ordinary create-page request. Use create_project_page_preview instead, including for '@VIXNODE-dev create a simple test page in [Brand Perfume]'. MULTI-PAGE PLANNING GATE: before any direct creation, determine whether the user's goal calls for multiple independently navigable pages or shared site-wide structure. When it does and the user has not approved an architecture, ask whether they want to plan the sitemap and shared Layout hierarchy first; do not call this tool until they answer. Skip that question only for an explicitly requested single page, landing page, or one-page site, or when the user already approved the structure. If planning is accepted, inspect existing pages and propose a Main Layout -> content-page hierarchy for approval. A Child Layout is optional, not required: include one only when a subset of pages needs an additional shared structure distinct from the Main Layout; otherwise attach content pages directly to the Main Layout. Create exactly one item per call in dependency order: pageType='layout' first; only when justified, pageType='childLayout' with layout=<main layout page id>; then pageType='layoutPage' with layout=<main layout page id> or, only for the relevant subset, <child layout page id>. Reuse returned page ids and never imply that one call creates the whole site. This exceptional tool writes immediately without a preview and may be used only after the assistant has already presented the exact current item, project, page settings, path, visibility, hierarchy relationship, and side effects, and the user then gives a separate explicit confirmation in a later message. Set userConfirmed=true only after that separate confirmation. If the user requests a preview in any language, never call this tool. This tool only creates one new saved page and its HTML, with Azure storage and GitHub history updates. It does not preview or publish. theme is stored metadata and cannot select another operation. Preview and confirmed UI execution are exposed as create_project_page_preview; publication is exposed as publish_project_page and publish_project. Call a publication tool only when publication was separately explained and explicitly confirmed. Check existing pages first because virtualPath plus fileName must be unique. Internal navigation rule for generated or modified HTML: same-project page links MUST use relative URLs without a leading slash (for example href=about instead of href=/about). A leading slash targets the shared domain root and loses the project publication prefix. Resolve destinations from actual virtualPath and fileName, account for nested page directories (for example ../about) and shared layout navigation, and do not invent routes or append .html unless the actual published URL uses it. Preserve fragment links, external absolute URLs, mailto/tel links, and unrelated asset/API URLs. Check affected internal links before submitting HTML.
create_project_page_preview
ChatGPTCOMPLETION RECEIPT EXCLUSION: If an app-generated message says an operation was already confirmed/submitted and requests a text-only receipt, do not call any tool and do not render another preview. Reply in text using the supplied management/public links. Supports preview and confirmed execute modes. Preview displays proposed changes; execute saves content and can publish it, so annotations cover the write-capable operation. Execution may publish with overwrite enabled; layout creation can republish affected existing pages and replace their live content. Follow the VIXNODE Website Builder Skill's planning, layout, HTML, preview, and confirmation workflow before calling this tool. Use this as the mandatory/default tool for every ordinary request to create, add, or build a project page, whether or not the user explicitly says preview. MULTI-PAGE PLANNING GATE: before generating HTML or calling any create-page tool, determine whether the user's actual goal calls for multiple independently navigable pages or shared site-wide structure. Signals include two or more requested destinations or recurring navigation areas such as Home, About, Products or Services, Blog, FAQ, and Contact. When a multi-page structure is likely and the user has not already approved a sitemap and layout hierarchy, explain briefly that shared layouts will keep navigation, header, footer, and styling consistent, then ask whether they want to plan the multi-page architecture first. Do not invoke this tool until they answer. Do not add this gate when the user explicitly requests a single page, landing page, or one-page site. If the user agrees, inspect existing project pages, propose a concise sitemap plus Main Layout -> content-page hierarchy, and wait for approval. A Child Layout is optional, not required: propose or create one only when a subset of pages needs an additional shared structure distinct from the Main Layout; otherwise every content page should reference the Main Layout directly. Then create and review exactly one item at a time in dependency order: pageType='layout' for the Main Layout; only when justified, pageType='childLayout' with layout=<main layout page id>; then pageType='layoutPage' with layout=<main layout page id> or, only for the relevant subset, <child layout page id>. Reuse the returned page ids in later calls and never imply that one call creates the whole site. Before invoking this tool for the current item, generate its complete non-empty HTML document and send it in html; never send an empty string or placeholder and never open the review UI before the HTML is ready. For example, '@VIXNODE-dev create a simple test page in [Brand Perfume]' MUST call this tool with mode='preview', projectName='Brand Perfume', and the complete generated HTML; it MUST NOT call create_project_page. The user's initial create request is authorization to prepare this review UI, never confirmation for an immediate write. If the user requests a preview in any language, you MUST call this tool in preview mode and MUST NOT call create_project_page. Unless the user explicitly requests no publication, draft-only creation, or a private page, you MUST send publishAfterSave=true and public=true so both checkboxes are selected by default. It renders a review UI whose button performs the confirmed creation. Keep fileName separate from virtualPath and ensure their combination does not duplicate an existing project page. Internal navigation rule for generated or modified HTML: same-project page links MUST use relative URLs without a leading slash (for example href=about instead of href=/about). A leading slash targets the shared domain root and loses the project publication prefix. Resolve destinations from actual virtualPath and fileName, account for nested page directories (for example ../about) and shared layout navigation, and do not invent routes or append .html unless the actual published URL uses it. Preserve fragment links, external absolute URLs, mailto/tel links, and unrelated asset/API URLs. Check affected internal links before submitting HTML.
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-file
ChatGPTRetrieves one private project resource or one publicly published file. file_name includes its relative directory path.
get-file-library
ChatGPTRetrieves uploaded files from a selected project file library. Default project_id is empty, so no files are loaded until a project is selected. This retrieval operation does not create, modify, or delete website projects, pages, SEO settings, or media. Internal account storage-structure repair may write an empty projects.json index when account storage is missing; it does not add a project or change existing project entries.
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-video
ChatGPTRetrieves one project video (or thumbnail) for MCP widgets without relying on browser direct /API/GetVideo access.
get-video-library
ChatGPTRetrieves uploaded videos from a selected project video library. Default project_id is empty, so no videos are loaded until a project is selected. This retrieval operation does not create, modify, or delete website projects, pages, SEO settings, or media. Internal account storage-structure repair may write an empty projects.json index when account storage is missing; it does not add a project or change existing project entries.
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_docs
ChatGPTRetrieves VIXNODE platform operation guides and MCP tool reference data, including features, steps, FAQ, guide URLs, tool status, descriptions, and usage examples. Use the vixnode_mcp_tools entry and its tools array when deciding which VIXNODE tool matches a request; the catalog includes separate validate_project_domain, configure_project_domain, get_project_domain_status, and remove_project_domain entries, plus create_project_page_preview and modify_project_page_preview. Consult each entry status and the live tool definitions before invoking tools awaiting review. The response provides toolCount and dynamic statusCounts; stagingToolCount is retained for backward compatibility. Available doc ids: vixnode_mcp, vixnode_mcp_tools, create_website, custom_domain, invite_member, create_page, schedule_published_page, bandwidth_limit, ai_vision_generate_page, ai_assistance_modify_node, ai_assistance_explain_node, ai_assistance_ask_node, ai_assistance_generate_node, ai_assistance_generate_image, manage_external_nodes, filter_find_node, set_api_connection_data_source, setting_seo_metadata, view_restore_webpage_modification_history, manage_resource_files, manage_published_files.
get_project_domain_status
ChatGPTRead the configured domain's latest status from the external domain/SSL provider. If SSL is pending, return public DNS validation and setup records. Read-only query: does not save status into the project, change project settings or DNS records, attach or remove a domain, or publish pages. Use only after configure_project_domain succeeds; check for ACTIVE_SSL.
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
ChatGPTDirectly modifies a project's general settings without UI and without publishing pages. Changing appName or virtualPath creates new public URL mappings and removes previous mappings, so existing public URLs may stop working. This tool does not modify pages, custom domains, members, roles, or permissions. Only supplied inputs are updated; omitted or null values are ignored, while explicit empty strings clear optional string values. For bandwidth.startTime and bandwidth.endTime, convert the local date and time requested by the user from the user's applicable time zone to UTC before calling this tool, and send ISO 8601 UTC values ending in 'Z'.
modify_project_page
ChatGPTUpdates exactly one existing project page without publishing. Follow the VIXNODE Website Builder Skill's target-resolution, layout, and minimal-change workflow before calling this exceptional no-preview tool. Use it only after presenting the exact target, changes, and side effects, and then obtaining a separate explicit user confirmation to write immediately without preview. The initial request to modify a page—even a fully specified request—is not that confirmation and MUST use modify_project_page_preview by default. If the user requests a preview in any language, never call this tool. This tool only updates the selected saved page properties and optional HTML, with Azure storage and GitHub history updates. It does not preview or publish. theme is stored metadata and cannot select another operation. Preview and confirmed UI execution are exposed as modify_project_page_preview; publication is exposed as publish_project_page and publish_project. Call a publication tool only when publication was separately explained and explicitly confirmed. Obtain the latest HTML first and keep virtualPath plus fileName unique. If virtualPath is set or changed, the page must be published again for the new path to take effect. Internal navigation rule for generated or modified HTML: same-project page links MUST use relative URLs without a leading slash (for example href=about instead of href=/about). A leading slash targets the shared domain root and loses the project publication prefix. Resolve destinations from actual virtualPath and fileName, account for nested page directories (for example ../about) and shared layout navigation, and do not invent routes or append .html unless the actual published URL uses it. Preserve fragment links, external absolute URLs, mailto/tel links, and unrelated asset/API URLs. Check affected internal links before submitting HTML.
modify_project_page_preview
ChatGPTCOMPLETION RECEIPT EXCLUSION: If an app-generated message says an operation was already confirmed/submitted and requests a text-only receipt, do not call any tool and do not render another preview. Reply in text using the supplied management/public links. Supports preview and confirmed execute modes. Preview displays proposed changes; execute saves content and can publish it, so annotations cover the write-capable operation. Follow the VIXNODE Website Builder Skill's target-resolution, layout, minimal-change, preview, and confirmation workflow before calling this tool. Use this as the mandatory/default tool for every ordinary request to modify, update, or edit a project page, whether or not the user explicitly says preview. Always send projectName with the exact selected project display name so the review card identifies the project. An initial modification request is authorization to prepare this review UI, never confirmation for an immediate write. If the user requests a preview in any language, you MUST call this tool in preview mode and MUST NOT call modify_project_page. Unless the user explicitly requests no publication, draft-only updating, or a private page, you MUST send publishAfterSave=true and public=true so both checkboxes are selected by default. Always obtain the latest HTML first; the rendered review UI performs the confirmed update. Keep fileName separate from virtualPath and ensure their combination does not duplicate another project page. Internal navigation rule for generated or modified HTML: same-project page links MUST use relative URLs without a leading slash (for example href=about instead of href=/about). A leading slash targets the shared domain root and loses the project publication prefix. Resolve destinations from actual virtualPath and fileName, account for nested page directories (for example ../about) and shared layout navigation, and do not invent routes or append .html unless the actual published URL uses it. Preserve fragment links, external absolute URLs, mailto/tel links, and unrelated asset/API URLs. Check affected internal links before submitting HTML.
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.
project_info
ChatGPTRetrieves detailed information for one project owned by the authenticated user. The result intentionally excludes the pages field. Use get_project_pages separately when page information is needed. In user-facing messages, show the project name instead of project_id unless the user explicitly requests the ID.
publish_project
ChatGPTFollow the VIXNODE Website Builder Skill's publication and confirmation workflow before calling this tool. Republishes all currently public webpages in a project and skips non-public pages. Replaces their live published content with the latest saved versions, including shared layout changes. Use only when project-wide republication is required, for example after changing a Main Layout or optional Child Layout whose change affects multiple pages. Present the project-wide impact and obtain a separate explicit user confirmation, then set userConfirmed=true. This operation can take considerably longer. Prefer create_project_page_preview or modify_project_page_preview for ordinary page creation or editing.
publish_project_page
ChatGPTFollow the VIXNODE Website Builder Skill's publication and confirmation workflow before calling this tool. Use this only after evaluating the real context, presenting the exact target and the fact that a private page will be made public, and then obtaining a separate explicit user confirmation to publish immediately. An initial create, modify, or publish request is not by itself confirmation for this direct tool, and preview workflows must publish through their confirmed UI action. Never use it to satisfy a preview request. It replaces the live published version with the latest saved page content and makes a private page public. It publishes immediately without rendering a UI and may follow create_project_page or modify_project_page only when publication was separately explained and explicitly confirmed. Set userConfirmed=true only after that confirmation.
remove_project_domain
ChatGPTRemove the project's current custom-domain binding through the external provider, remove its routing mapping, and clear the project domain and virtualPath. The custom URL becomes unavailable. First call with confirm=false to receive the impact, obtain explicit user consent, then call with confirm=true. Without confirm=true an existing domain is not removed. A project without a configured domain returns unchanged. Does not publish pages.
switch_account
ChatGPTReconnect VIXNODE and choose a different account.
upload_file
ChatGPTUpload one file to the selected project file storage. For webpage-related resource files, prefer a private upload with isPublished=false. Only upload a public file when the user's requirement explicitly needs it and the target has been carefully confirmed. A public file is a live resource used by the published website, and uploading the same file path directly overwrites the existing live file.
upload_image
ChatGPTUpload one image to the selected project photo library.
upload_video
ChatGPTUpload one video to the selected project video library. Uploading to an existing filename overwrites the stored resource and its thumbnail. Storage can expose the uploaded resource through a public Blob URL; do not upload confidential content. Confirm the target filename before replacing a resource.
validate_project_domain
ChatGPTCheck subscription eligibility and public DNS A/TXT records for the specified project and domain. For the same domain already attached to this project, return the latest provider status instead; ACTIVE_SSL needs no further attachment. Read-only validation: does not change project settings or DNS records, attach or remove a domain, or publish pages. Returns required DNS setup records when validation is incomplete. After successful validation of an unattached domain, use configure_project_domain with the same project and domain.
