@wix/mcp 1.0.27 → 1.0.29

package/build/cjs/index.cjs

@@ -36114,7 +36114,8 @@ var defaultToolDescriptions = {
     ${SYSTEM_REMINDER}
   `,
   CallWixSiteAPI: dedent_default`
-    Call Wix apis on a business or site. Use this to create, read, update, and delete data and other Wix entities in your Wix site,
+    Call Wix apis on a business or site. Use this to create, read, update, and delete data and other Wix entities in your Wix site.
+    For POST/PATCH/PUT requests, pass the request body as a JSON object 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"}}).
     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:
@@ -36131,6 +36132,7 @@ var defaultToolDescriptions = {
   `,
   ManageWixSite: dedent_default`
     Use 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 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"}}).
     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.
     ${SYSTEM_REMINDER}
@@ -36525,7 +36527,7 @@ var paramDescriptions = {
       `Docs urls like https://dev.wix.com/docs/... are not API urls, if you want to read the docs, use the "ReadFullDocsArticle" tool`
     ].join("\n"),
     method: "The HTTP method to use for the API call (e.g. GET, POST, PUT, DELETE)",
-    body: 'The request body object. YOU MUST NEVER MAKE UP A BODY - the body should be based on the conversation context, i.e from the user prompt OR got into the conversation context by the "ReadFullDocsArticle" tool OR by the "ReadFullDocsMethodSchema" tool - i.e based on the API docs, a relevant recipe you read (preferably), a code example you found in the docs, a schema you read etc.. YOU MUST NEVER ASSUME YOU KNOW WHAT THE BODY SCHEMA IS WITHOUT CONCRETE EXAMPLES OR SCHEMA DEFINITIONS FROM THE CONVERSATION CONTEXT. Prefer reading relevant recipes if you have them in context for understand the body schema for API calls.',
+    body: 'The request body as a JSON object with all the required fields and values, including nested objects. Pass the actual object, NOT a JSON string. YOU MUST NEVER MAKE UP A BODY - the body should be based on the conversation context, i.e from the user prompt OR got into the conversation context by the "ReadFullDocsArticle" tool OR by the "ReadFullDocsMethodSchema" tool - i.e based on the API docs, a relevant recipe you read (preferably), a code example you found in the docs, a schema you read etc.. YOU MUST NEVER ASSUME YOU KNOW WHAT THE BODY SCHEMA IS WITHOUT CONCRETE EXAMPLES OR SCHEMA DEFINITIONS FROM THE CONVERSATION CONTEXT. Prefer reading relevant recipes if you have them in context for understand the body schema for API calls.',
     reason: "One sentence explaining the original user request and why you are calling this API to complete it.",
     sourceDocUrl: [
       "The URL of the documentation or recipe where you found this API endpoint.",
@@ -36543,7 +36545,7 @@ var paramDescriptions = {
   ManageWixSite: {
     url: "The url of the api to call - ALWAYS get the information from the Wix REST docs DONT GUESS IT, the URL MUST BE ABSOLUTE URL",
     method: "The HTTP method to use for the API call (e.g. GET, POST, PUT, DELETE)",
-    body: 'The request body object. YOU MUST NEVER MAKE UP A BODY - this should be based on the conversation context, i.e from the user prompt or from the "WixREADME" tool or from the "SearchWixRESTDocumentation" tool or from the "BrowseWixRESTDocsMenu" tool or from the "ReadFullDocsArticle" tool or from the "ReadFullDocsMethodSchema" tool - i.e based on the API docs. YOU MUST NEVER ASSUME YOU KNOW WHAT THE SCHEMA IS WITHOUT CONCRETE EXAMPLES OR SCHEMA DEFINITIONS FROM THE CONVERSATION CONTEXT.'
+    body: 'The request body as a JSON object with all the required fields and values, including nested objects. Pass the actual object, NOT a JSON string. YOU MUST NEVER MAKE UP A BODY - this should be based on the conversation context, i.e from the user prompt or from the "WixREADME" tool or from the "SearchWixRESTDocumentation" tool or from the "BrowseWixRESTDocsMenu" tool or from the "ReadFullDocsArticle" tool or from the "ReadFullDocsMethodSchema" tool - i.e based on the API docs. YOU MUST NEVER ASSUME YOU KNOW WHAT THE SCHEMA IS WITHOUT CONCRETE EXAMPLES OR SCHEMA DEFINITIONS FROM THE CONVERSATION CONTEXT.'
   },
   SearchWixWDSDocumentation: {
     searchTerm: "The search term to search for in the Wix Design System Documentation",
@@ -39304,7 +39306,6 @@ function createWixToolkit(options) {
     docs,
     api,
     defaults = {},
-    curryFields = [],
     exclude = [],
     clientName,
     hooks
@@ -39344,7 +39345,7 @@ function createWixToolkit(options) {
   } else {
     addApiCallTool(server, authStrategy);
   }
-  const fieldsToRemove = [...Object.keys(defaults), ...curryFields];
+  const fieldsToRemove = Object.keys(defaults);
   const allTools = captured.filter((t) => !exclude.includes(t.name)).map((captured2) => {
     const inputSchema = fieldsToRemove.length > 0 ? buildSchemaWithout(captured2.paramsSchema, fieldsToRemove) : external_exports.object(captured2.paramsSchema);
     const execute = async (args) => {