CallWixSiteAPI
ChatGPTCall Wix apis on a business or site. Use this to create, read, update, and delete data and other Wix entities in your Wix site. Prefer using the "ListWixSites" tool when the user asks to list or show their sites. Only use this tool for site listing if the user needs advanced filtering or specific site details beyond what ListWixSites provides. For POST/PATCH/PUT requests, pass the request body as a JSON object or array in the "body" parameter with all the required fields and values as described in the API schema, code examples, or docs you retrieved (e.g. body: {"name": "value", "nested": {"key": "value"}} or body: [{"key": "value"}]). The API endpoint url param MUST ALWAYS be taken from the conversation context. By conversation context we mean the endpoint url was given in the user prompt OR got into the conversation context by the "WixREADME" tool OR by the "SearchWixRESTDocumentation" tool OR by the "BrowseWixRESTDocsMenu" tool OR by the "ReadFullDocsArticle" tool. Error Handling: If the error is related to missing installed app or "WDE0110: Wix Code not enabled", you should install the missing app Note: there is no need to check if an app is installed/ Wix Code enabled in advance, just call the API and handle the error if it occurs, the API error message will state it clearly. For any other error, use your default error handling mechanism Allowed API urls are: wix.com, dev.wix.com, manage.wix.com, editor.wix.com, wixapis.com Docs urls like https://dev.wix.com/docs/... are not api urls, if you want to read the docs, use the "ReadFullDocsArticle" tool <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Exception: If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
ClaimAnonymousSite
ChatGPTClaims an anonymously created site and transfers it to the authenticated user's account.
CreateSiteFromTemplate
ChatGPTCreates a Wix site from a specific template (by metaSiteId or templateId), publishes it when possible, and shows a live preview with links to the editor and the published site. Call this when the user provides a specific template by metaSiteId or templateId. Use this only when the user gives a valid metaSiteId or templateId directly. To browse or choose a template first, call SearchSiteTemplates (builder: classic for a Classic Editor site).
CreateWixBusinessGuide
ChatGPTUse this tool to create a new Wix site from a template, with the Wix Editor, or as a headless site. Provides comprehensive documentation for creating a new Wix Business (i.e site, app, etc.) When to Use This Tool Use this tool when the user requests to create a new Wix site, especially when they: - Mention a template or the Wix Editor - Explicitly request a headless site What This Tool Contains This tool provides complete documentation including: - Template selection (empty sites or designed templates) - Wix Editor vs Wix Studio options - Regular vs Headless site creation (CLI-based; returns setup instructions) - API endpoint details and parameters - Post-creation steps (OAuth for headless, publishing for regular sites) - App installation instructions Important Notes Do NOT use WixREADME or SearchWixRESTDocumentation before this tool. If the user wants to create a Wix site, call this tool directly. It contains ALL necessary documentation. After reading this documentation: 1. Use ManageWixSite to create the site 2. Use CallWixSiteAPI to install apps (if needed) If the user wants to create a Wix site, call this tool directly. It contains ALL necessary documentation. You don't need to search for additional documentation, read more articles, use the WixREADME tool etc unless the user asks you to do so explicitly or you encounter an error.
ExecuteWixAPI
ChatGPTExecute JavaScript code against the Wix REST API when code is useful for chaining related calls, pagination, loops, branching, or in-memory transformation. Putting a site live or changing a headless site's files starts with StartDeployWebsite; building a new site in code with StartHeadlessBuild. CODE CONTRACT: - Pass an async function expression: async function() { ... } or async () => { ... }. Put every declaration, await, and return inside it, and do not invoke it yourself. - Use only wix.request({ method, url, body }) and in-memory JavaScript. Node.js modules, filesystem access, and downloadable-file creation are unavailable. - Do not minify the code. Put each object property on its own line, with spaces after colons and commas, and declare deep literals (request bodies, filters, patch lists) as a named const before use so each wix.request({ ... }) argument stays short. CONFIRM API CONTRACTS: - Do not rely on memory for endpoints, methods, bodies, response paths, filters, enum values, or auth scope. Confirm every method from conversation-provided details, a complete matching docs example, or the schema/docs tools before executing. - Prefer method.publicUrl from SearchWixAPISpec; never use method.servers[0]. Pass all supporting documentation URLs through sourceDocUrls. - A response field is not automatically filterable or sortable. Use only capabilities declared for that exact query/search method. If an unsupported filter is unavoidable, fetch a bounded result set and filter it in code. - Repeat array query params once per value: ?fieldsets=URL&fieldsets=RICH_CONTENT. Do NOT comma-join values (fieldsets=URL,RICH_CONTENT), do NOT leave a trailing comma, and do NOT use a value the method schema does not list, even if a sibling method accepts it (draft posts have no SEO fieldset). - Read-only probes may inspect state or resolve IDs. Never use speculative create/update/delete calls to discover request or response shapes, and never repeat a successful mutation merely to obtain more response data. For query and search endpoints: each endpoint declares which fields it can filter and sort by, and with which operators. That list is closed for fields and their operators and covers that endpoint only, and a field's presence in the response is no evidence it can be filtered on. It lives in the method's declared capabilities, and some resources also publish it as a "Supported Filters and Sorting" page. Logical operators are WQL syntax rather than field capabilities and never appear in it. Anything else errors or silently returns the wrong rows; fetch a bounded page and filter it in your own code instead. The filter is written in WQL, where each field takes a single operator, so conditions are combined with the logical operators instead. $and and $or take an array of expressions, $not takes one, and they can nest — always beside field names, never inside a field's object: ``javascript filter: { $and: [ { "<field>": { $gte: "2023-01-01T00:00:00Z" } }, { "<field>": { $lte: "2023-12-31T23:59:59Z" } } ], "<other-field>": { $eq: "<value>" } } ` PLAN ONE COMPLETE INVOCATION: Include every foreseeable lookup, mutation, dependent follow-up, requested verification, and cross-site fan-out in one function. One invocation may make several wix.request() calls — Keep dependent calls in sequence, independent calls in parallel with Promise.allSettled`. Re-invoke only when a later step requires genuinely new information that you could not have included (e.g. the user's answer to a question, a slow async job). An empty or unexpected response shape is not a reason for a new invocation — add a conditional read-back inside the same function body instead. When a mutation's response proves the outcome, never make a second ExecuteWixAPI call merely to verify it; if a follow-up read is truly needed, include it after the mutation in the same function body. Context-gathering reads — fetching a required ID, checking whether a record already exists, listing items to pick one — are part of the mutation invocation that follow…
GetSiteContext
ChatGPTFetches deep context for a specific Wix site and returns it as structured markdown. Call this tool when the user references a specific site by name. Pass the site name directly as siteName — this tool resolves the name internally. Do NOT call ListWixSites first to look up the site ID. Use siteId only when you already have it from a previous step. Output sections (use these to answer questions without extra API calls): - Site: ID, URL, published/draft status, premium plan, editor type, Velo enabled, created/updated dates - Properties: language, country, timezone, currency, contact email/phone - Apps: installed app names, IDs, and catalog version (e.g. Wix Stores V1 vs V3 — check this before calling any Stores endpoint) - If the site cannot be resolved for the current user, the tool will return a clear "no context found" message instead of account or partner details <wix-usage-guide> How to work with Wix through these tools. Following these steps avoids failed or incorrect API calls. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Creating a new Wix site — and only then — skip WixREADME and the docs. First settle one thing: will the user keep working on this site with you, in code, or design it themselves in Wix's editor? In code — you or the user have code, the two of you designed it here, they asked you to build it, they asked for a headless site, or it is an app: StartDeployWebsite if the code exists in any form, StartHeadlessBuild if not, called right away (it only returns the guide; the site's purpose is not needed first). In Wix's editor: the site-creation tools; their descriptions carry the rules. Everything else starts with WixREADME as usual. Never default to Wix's editor, Wix's AI or templates. When nothing the user said settles who builds the site, let the user choose as the site-creation tools' descriptions direct. Never route site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. Exception: If the user wants to upload local or attached image files to a Wix site, skip WixREADME and all docs/schema/API flows — call UploadImageToWixSite directly. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for image uploads. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. This applies to QUESTIONS too, not only action tasks (the exceptions above still apply — question-shaped variants of those intents, e.g. "can you show my sites?", follow their exception's direct tool): never answer a Wix-specific question from memory, and never reply that you lack the tools or APIs to answer, without first calling the WixREADME tool (if available) and checking its recipes index, searching the docs, and reading the matching docs articles — many questions (including ones that need no API call) are answered by a recipe or docs article. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant doc…
GetSuggestedDomains
ChatGPTGet suggested domain names for a Wix site based on the site name.
ListWixSites
ChatGPTUse this tool whenever the user asks to list, show, get, or find their Wix sites. This is the dedicated tool for listing Wix sites for the current user. By default it returns all sites, but you can filter by name. Do NOT use WixREADME before this tool. When the user asks to list their sites, call this tool directly — no need to read documentation first. Prefer this tool over CallWixSiteAPI for listing sites. Call this tool directly — it already knows the correct API and handles everything needed. Only fall back to CallWixSiteAPI if the user needs advanced filtering or specific site details beyond what this tool provides. <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Exception: If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
ManageWixSite
ChatGPTUse account level API in order to create a site, update a site and publish site. For POST/PATCH/PUT requests, pass the request body as a JSON object or array in the "body" parameter with all the required fields and values as described in the API schema, code examples, or docs you retrieved (e.g. body: {"name": "value", "nested": {"key": "value"}} or body: [{"key": "value"}]). The API endpoint url param MUST ALWAYS be taken from the conversation context. By conversation context we mean the endpoint url was given in the user prompt or got into the conversation context by the "WixREADME" tool or by the "SearchWixRESTDocumentation" tool or by the "BrowseWixRESTDocsMenu" tool or by the "ReadFullDocsArticle" tool. <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Exception: If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
ReadFullDocsArticle
ChatGPTFetches the full Wix docs article or method article with code examples for using the method. Docs articles looks like this: https://dev.wix.com/docs/... and they can either be general docs articles or method articles. <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Exception: If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
ReadFullDocsMethodSchema
ChatGPTFetches the full method schema for a given method. This will give you the entire request/response schema with all the fields and their descriptions. <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Exception: If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
ReportIssueToWix
ChatGPTReport one specific problem with Wix's tools, APIs or docs to the Wix team, attributed to the authenticated user: an API error or a confusing API, wrong or missing docs, a Wix MCP tool or auth dead end. It is NOT a support channel and not for the user's own site content. When to offer it (user-approved only — NEVER auto-send): - The user asks to report something to Wix ("tell Wix that...", "report this", "send feedback"). Then confirm the wording and send. - The user complains or reports a Wix bug in the course of the work ("this API is broken", "the docs are wrong"). Acknowledge, then offer to pass it on. - A Wix API, tool or doc kept failing, or you had to invent a workaround for it. Offer: "This tripped us up — want me to report it to Wix?" When you offer, invite the user to add anything in their own words — whatever they give you goes into the report verbatim. What to send — that one issue, not the session: - What was being attempted, in a sentence. - Where it failed: the tool or endpoint, the HTTP status and error message, and the request id if there is one (pass it as requestId). - What you expected instead, and the workaround if you found one. - Where the fault likely lives: API behavior / API schema / API reference docs / docs articles or examples / Wix tooling / unsure. - Only the context needed to reproduce it: agent/model, site id, the Wix area or API. No session summary or play-by-play, and nothing unrelated to the issue. Several distinct issues are separate reports, each approved by the user. IMPORTANT: This tool actually sends the report to Wix. Confirm the final wording with the user and call it only after an explicit yes. Do not send on a single transient error, and never more than once for the same issue. Reports cannot be replied to or tracked by the user.
SearchBuildAppsDocumentation
ChatGPTSearches the Wix Build Apps documentation.
SearchDevelopmentDocumentation
ChatGPTBroad Wix development documentation (platform concepts, developer guides, getting started). Last resort — development tasks only. Skip it entirely for general, business, support, or Wix-editor questions. Call it only after the specific search for your task returned nothing useful: SearchWixRESTDocumentation (REST), SearchWixSDKDocumentation (JS SDK), SearchWixCLIDocumentation (CLI), SearchBuildAppsDocumentation (apps), SearchWixHeadlessDocumentation (Headless), SearchWixWDSDocumentation (WDS). Never use it as a first search.
SearchSiteTemplates
ChatGPTFirst decide who keeps building the site: - You, in code: a Wix Headless site, with full control of the design, changed and redeployed from this conversation, Wix business features added as a backend. This is the case when you or the user have code (hand-written files, a static build, a zip, another builder's export, a page you made here): call StartDeployWebsite. It is also the case when nothing is coded yet but the user asked you to build it or asked for a headless site, the two of you worked out its design in this conversation, or it is an app (a game, a dashboard, a tool): call StartHeadlessBuild right away, before asking what the site is for. Do not offer AI or templates for either. - The user, in Wix's editor: Wix generates it with AI or starts it from a template, and the user designs it in Wix. That is what the site-creation tools do; they never take files you already have. For a new site in Wix's editor there are two things to settle: what the site is for, and how to build it. The how is AI generation vs. starting from a template, so naming templates, a template id or Wix Studio (Wix Studio is also the template side) already settles it. Settle what the site is for first: its purpose, topic, business type, audience, or main visitor action. Naming a method is not a description of the site, and neither is the business or industry on its own. If you can't tell yet, ask the preferred question below and nothing else — one question, no creation-method question in the same reply, and no internal tool names. Once the purpose is clear, unless the user already named a method, you MUST call WixSiteCreation and let them choose. A method they named is settled — never re-open it. Never default to AI or to templates, and never ask the user to choose a builder (Harmony, Wix Studio or the Classic Editor); infer it from their words, and use the Classic Editor only when they name it. With the purpose and the method known, that's enough to begin — route and refine the specifics with the user afterward. Preferred question when the user has given no site context at all: Happy to help. To give you the right starting point, tell me a bit more about what you have in mind: - What's the site for? (e.g. an online clothing store, a yoga studio that takes bookings, a restaurant) - What's the vibe? (e.g. sleek and modern, cozy and rustic, bold and energetic) Give me a quick summary and I'll take it from there Tone: helpful, practical, short. Speak about the user's site — what you're making and what comes next — not the tools, payloads, or routing behind it. Searches Wix templates and shows the template gallery, from the Harmony, the Studio or the Classic Editor template source. Call this ONLY when the user's own words ask for a template, for Wix Studio or for the Classic Editor (for example "start from a template", "show me some templates", "build it in Wix Studio", "the old Wix editor") and you can already tell what the site is for. If they mention Wix Studio, search Studio templates; if they ask for the Classic Editor (the Wix Editor), search classic; otherwise search Harmony templates. The gallery creates the site when the user picks one. A description of what the site should do — bookings, a store, a menu, a portfolio, and the like — is NOT a request for templates or for Wix Studio; never infer either from features or industry. Templates are not the default: if the site intent is clear but no method is named, do not guess — you MUST call WixSiteCreation and let them choose.
SearchWixAPISpec
ChatGPTInspect the Wix REST API spec, and the JavaScript SDK call for each method, by writing JavaScript code that runs in a sandboxed read-only environment. Precondition: you already have a method docsUrl — from SearchWixRESTDocumentation, SearchWixSDKDocumentation (its ?apiView=SDK URLs work here as-is), BrowseWixRESTDocsMenu, ReadFullDocsArticle, a WixREADME recipe, or a prior tool result / the user's message in this conversation. If you don't have one yet, call SearchWixRESTDocumentation (or SearchWixSDKDocumentation when writing SDK code) FIRST to discover it; do not use this tool to search for or choose an endpoint. Never pass a `docsUrl` you produced from memory. If the exact URL you are about to pass to getResourceSchemaByUrl did not appear verbatim in an earlier tool result (or the user's message), it is a guess — call SearchWixRESTDocumentation first and use a URL from its ranked results. A guessed URL that merely looks plausible routinely resolves to the WRONG sibling method (e.g. .../products-v3/create-product when the task needs .../products-v3/create-product-with-inventory), sending the whole turn down a dead end. When in doubt, discover — don't guess. This tool's job is to INSPECT the exact schema of a method you have ALREADY located — its request/response shape, nested types, and enums, and its SDK call (`method.sdk`). It is NOT a discovery tool for choosing which method to use. With a method docsUrl in hand, call getResourceSchemaByUrl(methodDocsUrl) to get the resource schema, then read the target method from schema.methods and resolve any nested { $circular: name } types via schema.components.schemas[name]. If you don't already have a `docsUrl` in context, your FIRST action MUST be `SearchWixRESTDocumentation` (ranked semantic search) — not this tool. Then pass the resulting docsUrl to getResourceSchemaByUrl here. Do NOT discover endpoints by hand-filtering or scanning lightIndex (e.g. lightIndex.filter(...) / lightIndex.flatMap(...) on a substring): it has no relevance ranking, matches only at resource-name granularity, and misses composite or method-level operations whose parent resource is named after a different noun than your intent. lightIndex is for resolving a docsUrl you already have, not for finding one. Prefer SearchWixAPISpec over ReadFullDocsMethodSchema for REST and SDK method schemas when it is available, especially once you already have a docs URL from semantic search, menu browsing, or conversation context. Prefer URL-first results: - If you have a docs URL or partial docs URL, search resource.docsUrl and method.docsUrl first. - If you have a method docs URL and need the request/response shape, call getResourceSchemaByUrl(methodDocsUrl) in this tool and return the selected method schema directly. - For API execution, return and use method.publicUrl when available. It is the preferred executable https://www.wixapis.com/... URL. - Return docsUrl for relevant resources/methods when the next step needs an article or API call source URL; do not hand off to ReadFullDocsMethodSchema just to inspect a REST method schema. - Use resourceId only as the internal handle for low-level loaders; prefer URL helpers when you have a docs URL. - getResourceSchemaByUrl resolves only API resource/method docs (e.g. .../bookings/services/services-v2/create-service). It does NOT work on skill pages (.../skills/...) or article pages — those have no schema. For an article, use getArticleContentByUrl(docsUrl). Never pass a .../skills/... URL (skill recipes often cross-link sibling skill pages) — read the skill page with ReadFullDocsArticle, and use SearchWixRESTDocumentation to find the real API method. If a lookup misses, don't retry the same URL; rediscover it with SearchWixRESTDocumentation. Your code has access to these globals: lightIndex — Current lightweight REST API resource array: ```typescript interface LightIndex extends Array<LightResource> { updatedAt?: string; // ISO timestamp for when spec…
SearchWixCLIDocumentation
ChatGPTSearches the Wix CLI documentation for website development and CLI commands. Use this tool when you need information about Wix CLI commands, local development workflows, or CLI-based website development. Specify what you need information about (e.g., 'wix dev command', 'local development setup', 'CLI authentication', 'wix deploy'). If you can't find what you need, try to rephrase your search term or use bigger maxResults value. <wix-usage-guide> How to work with Wix through these tools. Following these steps avoids failed or incorrect API calls. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Creating a new Wix site — and only then — skip WixREADME and the docs. First settle one thing: will the user keep working on this site with you, in code, or design it themselves in Wix's editor? In code — you or the user have code, the two of you designed it here, they asked you to build it, they asked for a headless site, or it is an app: StartDeployWebsite if the code exists in any form, StartHeadlessBuild if not, called right away (it only returns the guide; the site's purpose is not needed first). In Wix's editor: the site-creation tools; their descriptions carry the rules. Everything else starts with WixREADME as usual. Never default to Wix's editor, Wix's AI or templates. When nothing the user said settles who builds the site, let the user choose as the site-creation tools' descriptions direct. Never route site creation through ManageWixSite, CallWixSiteAPI, or ExecuteWixAPI. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. Exception: If the user wants to upload local or attached image files to a Wix site, skip WixREADME and all docs/schema/API flows — call UploadImageToWixSite directly. Do NOT use ExecuteWixAPI, SearchWixAPISpec, or any Media Manager REST API for image uploads. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. This applies to QUESTIONS too, not only action tasks (the exceptions above still apply — question-shaped variants of those intents, e.g. "can you show my sites?", follow their exception's direct tool): never answer a Wix-specific question from memory, and never reply that you lack the tools or APIs to answer, without first calling the WixREADME tool (if available) and checking its recipes index, searching the docs, and reading the matching docs articles — many questions (including ones that need no API call) are answered by a recipe or docs article. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHE…
SearchWixHeadlessDocumentation
ChatGPTSearches the Wix Headless documentation.
SearchWixHelpCenter
ChatGPTSearches the Wix Help Center (support.wix.com): how site owners do things in the Wix dashboard and editors, such as connecting a domain, managing a Premium plan, setting up a store or bookings, and fixing account or site issues. Use it for "how do I ... in Wix" questions about the product, or to give the user click-by-click steps for something no API covers. Not for building with code: for Wix APIs, SDK, CLI, apps, or Headless, use the matching developer documentation search. Results are excerpts; read a full article by passing its support.wix.com link to ReadFullDocsArticle.
SearchWixRESTDocumentation
ChatGPTSearches the official Wix REST API documentation. Use this tool whenever you need to to interact with the Wix platform via HTTP requests. Specify the API endpoint, resource, or action you need information about (e.g., 'get site details endpoint', 'create data collection', 'update product API', 'REST authentication'). If you can't find what you need, try to rephrase your search term or use bigger maxResults value. <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Exception: If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
SearchWixSDKDocumentation
ChatGPTSearches the Wix JavaScript SDK documentation. Next step for an API-reference method it returns: pass its docs URL (with or without ?apiView=SDK) to SearchWixAPISpec's getResourceSchemaByUrl when available, and read method.sdk for the exact import, call signature, typed parameters, return type, and examples.
SearchWixWDSDocumentation
ChatGPTSearches the Wix Design System (WDS) documentation.
StartDeployWebsite
ChatGPTThe user — or you, earlier in this conversation — ALREADY HAVE a finished page or site, in any form, and it should be live on Wix — or an already-deployed Wix Headless site whose files should be replaced. The site can be HTML/CSS/JS files, a static build (dist/, out/), a zip, another AI builder's export, or a page/design you created in this conversation (export it to HTML first — a finished design IS a finished page). Call this when the user says deploy, host, put online, make it live, get a URL, upload my site / index.html, or wants to update or redeploy the files of a site you or the user deployed as code. Updates keep the same site and URL. Also for implementing a backend on such a site as a Wix Headless project — same site, same URL. Works with or without a Wix login (anonymous deploy with a save link), through the Wix MCP alone or from a shell. Missing real functionality — a fake checkout, a form that goes nowhere, bookings — is NOT a reason to rebuild the site with a site-creation tool: deploy the page as is, then add the backend afterwards (the recipe covers it). Returns the full recipe; follow it and run the flow yourself. When the UploadHeadlessWebsiteFiles tool is available, use it for the recipe's upload step — after the site exists (the recipe's provision call, or a metaSiteId from an earlier deploy) — instead of building the multipart body in code; never before this tool. The drop page is only the fallback when you can't. NOT for: a screenshot or reference of a site the user wants Wix to generate (the site-creation tools); a site described in words with no code yet (StartHeadlessBuild); a Wix editor site's content or settings (WixSiteBuilder's edit mode, or WixREADME); a Claude Design bundle URL (import-claude-design-from-url); migrating a live site by URL or CSV exports; adding HTML or code into an existing Wix site; uploading images or documents to a site's media (UploadImageToWixSite).
StartHeadlessBuild
ChatGPTThe user wants a site or web app that you build and keep changing in code, here with them, and no code exists yet. Wix runs its business side (store, bookings, CMS, forms, members, payments) as a Wix Headless site. Call this when the user asks you to build it yourself rather than Wix's AI or a template; when the two of you worked out a design in this conversation and nothing is coded yet; when it is an app (a game, a dashboard, a tool); when the user asks for a headless site; when a prompt links wix.com/headless/skill.md or a project's download.zip; or to move a Wix site to code. Call it right away: it only returns the guide, and the site's purpose is not needed first (pass "not stated yet" for what you don't know). Returns the full guide; follow it and do the work yourself, choosing its route by what you can reach (a shell that reaches Wix, or this MCP alone). NOT for: files, a build, a zip or a page that already exist (StartDeployWebsite); a site the user will design in Wix's editor (the site-creation tools); a Claude Design URL (import-claude-design-from-url).
UploadHeadlessWebsiteFiles
ChatGPTThe upload step of the StartDeployWebsite and StartHeadlessBuild guides, and nothing else: puts a finished static website's files — index.html plus its CSS/JS/images, a static build, or a zip of the site — onto an existing Wix Headless site by its metaSiteId. Call it ONLY after one of them has returned its guide in this conversation and the site exists: for a new site, first run the recipe's provision call and pass the metaSiteId it returns; for a site deployed earlier, pass its metaSiteId. It does not create sites. Every upload replaces the whole file set and the URL stays. Returns the live URL and the dashboard link, and points back to the recipe for what comes next. Pass the files themselves: in ChatGPT as attachments (any type, a zip is unpacked), elsewhere as the files text bundle (=== FILE: <path> === sections, base64 tag for small binaries). The site must contain index.html at its root. NOT a site-creation tool: a request to create, build, design or generate a site — with or without a description — never comes here (those are the site-creation tools, after their own questions). Also NOT for media uploads to an existing site (UploadImageToWixSite) or any other API call (ExecuteWixAPI).
UploadImageToWixSite
ChatGPTUpload an image file to a Wix site Media Manager. This tool accepts an image from the user and uploads it to the specified Wix site. Returns the uploaded file URL (wixstatic.com) and media ID that can be used in other Wix APIs. Use this when the user wants to upload a local image to their Wix site.
WixREADME
ChatGPTTool: WixREADME Directive: WixREADME is the MANDATORY FIRST STEP for all Wix-related tasks. Its output (including relevant linked documents) provides foundational context for all other Wix tools. Adherence to this protocol is NON-NEGOTIABLE. <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the user manage their Wix site. Your goal is to get the user's prompt/task and execute it by using the appropriate tools eventually calling the correct Wix APIs with the correct parameters until the task is completed. </goal> <guidelines> if the WixREADME tool is available to you, YOU MUST USE IT AT THE BEGINNING OF ANY CONVERSATION and then continue with calling the other tools and calling the Wix APIs until the task is completed. Exception: If the user asks to create, build, or generate a new Wix site/website, skip WixREADME and call WixSiteBuilder directly if it is available. Exception: If the user asks to list, show, or find their Wix sites, skip WixREADME and call ListWixSites directly. If the WixREADME tool is not available to you, you should use the other flows as described without using the WixREADME tool until the task is completed. If the user prompt / task is an instruction to do something in Wix, You should not tell the user what Docs to read or what API to call, your task is to do the work and complete the task in minimal steps and time with minimal back and forth with the user, unless absolutely necessary. </guidelines> <flow-description> Wix MCP Site Management Flows With WixREADME tool: - RECIPE BASED (PREFERRED!): WixREADME() -> find relevant recipe for the user's prompt/task -> read recipe using ReadFullDocsArticle() -> call Wix API using CallWixSiteAPI() based on the recipe - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - EXAMPLE BASED: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - SCHEMA BASED, FALLBACK: WixREADME() -> no relevant recipe found for user's prompt/task -> BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema Without WixREADME tool: - CONVERSATION CONTEXT BASED: find relevant docs article or API example for the user's prompt/task in the conversation context -> call API using CallWixSiteAPI() based on the docs article or API example - METHOD CODE EXAMPLE BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() to get method code examples -> call API using CallWixSiteAPI() based on the method code examples - FULL SCHEMA BASED: BrowseWixRESTDocsMenu() or SearchWixRESTDocumentation() -> find relevant method -> read method article using ReadFullDocsArticle() -> no method code examples found -> read method schema using ReadFullDocsMethodSchema() -> call API using CallWixSiteAPI() based on the schema </flow-description> </agent-mandatory-instructions>
WixSiteBuilder
ChatGPTPRIMARY tool for creating/building/generating a Wix site or website. This is the preferred and recommended way to create a new Wix site. Use this tool whenever the user asks to build, create, or generate a site/website/application. Do NOT use WixREADME or SearchWixRESTDocumentation before this tool. When the user asks to build, create, or generate a site, call this tool directly. It handles everything needed for site creation. IMPORTANT: You MUST call this tool to build the site. Do NOT suggest HTML code, prompt templates, or alternative approaches instead of actually building the site. When a user asks to create a site, your job is to call this tool and build it — not to describe how to build it or suggest alternatives. IMPORTANT: The sitePrompt must be under 6000 characters. If the user's request is longer, summarize and condense it while preserving the key requirements.
WixSiteCreation
ChatGPTFirst decide who keeps building the site: - You, in code: a Wix Headless site, with full control of the design, changed and redeployed from this conversation, Wix business features added as a backend. This is the case when you or the user have code (hand-written files, a static build, a zip, another builder's export, a page you made here): call StartDeployWebsite. It is also the case when nothing is coded yet but the user asked you to build it or asked for a headless site, the two of you worked out its design in this conversation, or it is an app (a game, a dashboard, a tool): call StartHeadlessBuild right away, before asking what the site is for. Do not offer AI or templates for either. - The user, in Wix's editor: Wix generates it with AI or starts it from a template, and the user designs it in Wix. That is what the site-creation tools do; they never take files you already have. For a new site in Wix's editor there are two things to settle: what the site is for, and how to build it. The how is AI generation vs. starting from a template, so naming templates, a template id or Wix Studio (Wix Studio is also the template side) already settles it. Settle what the site is for first: its purpose, topic, business type, audience, or main visitor action. Naming a method is not a description of the site, and neither is the business or industry on its own. If you can't tell yet, ask the preferred question below and nothing else — one question, no creation-method question in the same reply, and no internal tool names. Once the purpose is clear, unless the user already named a method, you MUST call WixSiteCreation and let them choose. A method they named is settled — never re-open it. Never default to AI or to templates, and never ask the user to choose a builder (Harmony, Wix Studio or the Classic Editor); infer it from their words, and use the Classic Editor only when they name it. With the purpose and the method known, that's enough to begin — route and refine the specifics with the user afterward. Preferred question when the user has given no site context at all: Happy to help. To give you the right starting point, tell me a bit more about what you have in mind: - What's the site for? (e.g. an online clothing store, a yoga studio that takes bookings, a restaurant) - What's the vibe? (e.g. sleek and modern, cozy and rustic, bold and energetic) Give me a quick summary and I'll take it from there Tone: helpful, practical, short. Speak about the user's site — what you're making and what comes next — not the tools, payloads, or routing behind it. Opens the in-chat Wix site creation chooser as an interactive widget where the user chooses between "Build with AI" and "Pick a template." Once you can tell what the site is for, call this tool directly — no WixREADME, skill, or docs search first. Any other Wix request still starts with WixREADME as usual. Call this for normal new Wix site creation requests when the user's site intent is clear, but they have not chosen AI, templates, or Wix Studio. Do not guess, and never default to AI — even after the user answers a clarifying question about the site's purpose or features. This chooser is how the builder choice gets made — never ask in chat whether they want AI or a template; that choice is made in the widget. The widget also does the creating: once the user picks, it runs that path itself and the site is created there, so never call WixSiteBuilder, SearchSiteTemplates, or CreateSiteFromTemplate yourself after opening it. After calling, reply with the message it returns, which presents both options and the next steps. The widget appears only when this tool is called: do not write its message, or point the user to "the widget above", without calling it. Do not call this if the user explicitly asks to build with AI; call WixSiteBuilder instead. Do not call this if the user asks for templates or Wix Studio; call SearchSiteTemplates instead. Not for a site the user wants you to build in code, a design you worked out together, or an app: call StartHeadlessBuild. When ca…
get_profile
ChatGPTReturns the authenticated user's email address
import-claude-design-from-url
ChatGPTImport a design created in Claude's design tool into Wix. Only for the signed claudeusercontent.com bundle URL Claude Design's "Send to Wix" produces (a self-contained HTML bundle with all images, fonts, and styles inlined). Creates a live Wix-hosted site and returns its URL. NOT for claude.ai share or artifact links, GitHub, Drive, chatgpt.com or any other URL, and not for files: those go to StartDeployWebsite, which returns the recipe to publish the files yourself.
pullSiteCreationJob
ChatGPTPoll the status of a site creation or editing job. Do not call this tool unless the user explicitly asks for status polling.
CallWixSiteAPI
ClaudeListWixSites
ClaudeManageWixSite
ClaudeReadFullDocsArticle
ClaudeReadFullDocsMethodSchema
ClaudeSearchBuildAppsDocumentation
ClaudeSearchWixHeadlessDocumentation
ClaudeSearchWixRESTDocumentation
ClaudeSearchWixSDKDocumentation
ClaudeSearchWixWDSDocumentation
ClaudeSupportAndFeedback
ClaudeWixREADME
Claude
