@bettercms-ai/mcp 0.41.0 → 0.41.1

package/dist/index.js

@@ -3171,7 +3171,20 @@ function buildToolDefs(deps) {
         "Edit a page",
         "Edit a page: title, slug, SEO metaTitle/metaDescription, publish status (draft|published), and `blockJson` (its block composition \u2014 passing it REPLACES the whole array, so read get_page first). It does NOT change the field SCHEMA \u2014 use add_page_field / set_page_content for that. Renaming the slug keeps content intact. Publishing copies the draft blocks live in the same call. " + SECTION_DOCTRINE,
         z.object({ pageId: z.string().min(1), title: z.string().optional(), slug: z.string().optional(), blockJson: z.array(blockObject).optional().describe("REPLACES the page's block composition"), metaTitle: z.string().optional(), metaDescription: z.string().optional(), status: z.enum(["draft", "published"]).optional() }).shape,
-        async (c, a) => ok("Updated page.", await data(c, "PATCH", `/management/pages/${s(a.pageId)}/meta`, { title: a.title, slug: a.slug, blockJson: a.blockJson, metaTitle: a.metaTitle, metaDescription: a.metaDescription, status: a.status }))
+        async (c, a) => {
+          const res = await c.fetchJSON(
+            c.url(`/management/pages/${s(a.pageId)}/meta`),
+            {
+              method: "PATCH",
+              body: JSON.stringify({ title: a.title, slug: a.slug, blockJson: a.blockJson, metaTitle: a.metaTitle, metaDescription: a.metaDescription, status: a.status })
+            }
+          );
+          const note = res.redirectNote;
+          return ok(
+            note ? `Updated page. An existing redirect from ${note.source} already points to ${note.existingDestination}; it wasn't changed, so the old address does not redirect to the new one.` : "Updated page.",
+            res.data
+          );
+        }
       ),
       // ── Code + deploy (parity with remote /mcp; needs artifact:write) ──
       // Both grant shapes carry that scope now; a workspace-wide one names its target per