VIXNODE

Follow 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.

publish_project_page

Retrieves 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. 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_all_project_pages

Retrieves 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_docs

Retrieves one private project resource or one publicly published file. file_name includes its relative directory path.

get-file

Retrieves 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-file-library

Retrieves one project image (or thumbnail) for MCP widgets without relying on browser direct /API/GetImage access.

get-image

Retrieves 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. 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-photo-gallery

Read 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_domain_status

Retrieves 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

Retrieves project page HTML content by version (commit sha).

get_project_page_html_by_version

Retrieves 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_html_history

Retrieves 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). 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_project_page_seo_setting

Retrieves 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. 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_project_pages

Retrieves the published HTML content of a specific page within a project.

get_published_page_html

Retrieves 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: 'change the style', 'switch themes', 'adjust the color palette', 'make it more modern', 'switch to a minimal style'), call this tool first to get candidate themes before proposing or generating modifications.

get_reference_themes

Retrieves 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_seo_data_structure_sample

Retrieves HTML content from a URL.

get_url_html

Retrieve information about a VIXNODE account, including email, display name, plan details, and quotas.

get_account_info

Retrieves one project video (or thumbnail) for MCP widgets without relying on browser direct /API/GetVideo access.

get-video

Retrieves 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-video-library

Retrieves a list of projects associated with the authenticated user's website. Page inventories and page counts are not included; omitted page data does not mean a project has zero pages. Role data describes permissions, not the project's page inventory. Use get_project_pages to retrieve actual pages before stating a page count or that a project has no pages. In user-facing messages, show project/page names instead of project_id/page_id unless the user explicitly requests those IDs. 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_website_projects

Directly 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

COMPLETION 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.

modify_project_page_preview

Modifies and publishes SEO settings for a specific VIXNODE page. Before invoking this tool, present the exact proposed SEO tags and JSON-LD structured data to the user and obtain explicit approval in the conversation. The preview UI is read-only and does not apply changes. Call this tool only after the user clearly asks to proceed. After completion, call get_project_page_seo_setting so the user can review the published result.

modify_project_page_seo_setting

Modify an existing web page under a specific project and publish the latest HTML content. For new project-page update workflows, prefer modify_project_page_preview, which supports independent virtualPath and fileName fields, UI or conversational confirmation, and optional publication after update. Use modify_web_page only when compatibility with the legacy webpage modification workflow is required. IMPORTANT: Before regenerating the page HTML for any modification, ALWAYS call get_project_page_html first to fetch the latest saved design 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 explicit user confirmation. Use the existing UI path with confirmationMethod='ui', confirmByUser=true, and a valid confirmToken, or, after presenting the exact modification and obtaining the user's explicit agreement in the conversation, use confirmationMethod='conversation' and userConfirmed=true. Never infer conversational confirmation from an ambiguous request. If confirmationMethod is omitted, the existing UI confirmation path is used. If HTML is truncated and cannot be previewed correctly, ask the user to try ChatGPT Work mode: https://chatgpt.com/?surface=work. 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. A page created by create_web_page can later be updated without publishing through modify_project_page, then published through publish_project_page when explicitly requested. Input keys (only): project_id, page_id, name, fileName, public, pageType, layout, lang, html, confirm, confirmByUser, confirmToken, confirmationMethod, userConfirmed. 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.

modify_web_page

Retrieves 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.

project_info

Follow 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

Remove 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.

remove_project_domain

Initiate VIXNODE account reconnection by returning an authentication challenge to the client. The user chooses the account through the client authorization flow. This does not delete account content or revoke credentials by itself.

switch_account

Upload 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_file

Upload one image to the selected project photo 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.

upload_image

Upload 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.

upload_video

Check subscription eligibility and public DNS A/TXT records for the specified project and domain. 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, use configure_project_domain with the same project and domain.

validate_project_domain