@bettercms-ai/mcp 0.55.1 → 0.56.1

package/dist/index.js

@@ -2582,6 +2582,7 @@ var LISTING_TAIL = /* @__PURE__ */ new Set([
   // claims with. Ten more tools than the tail was written for, and a connector that truncates
   // would otherwise lose `get_deploy_status` and the GitHub lane to make room for them.
   "research_account",
+  "build_abm_page",
   "claim_abm_task",
   "complete_abm_task",
   "fail_abm_task",
@@ -3890,6 +3891,33 @@ ${res.warnings.join("\n")}` : summary, res.data);
         }).shape,
         async (c, a) => ok("Account brief.", await data(c, "POST", `/management/campaigns/research`, { campaignId: a.campaignId, domain: a.domain, name: a.name, mode: a.mode, force: a.force }))
       ),
+      def(
+        "build_abm_page",
+        "Build one ABM page for one account",
+        "Build ONE personalized page for ONE account, guided: give the sales motion and a paragraph of context about the target ('Lumina \u2014 300-rep sales team moving off spreadsheets\u2026') and this mints the campaign, the page, the collection and the run. `brandUrl` learns the seller's brand first, once per project, and needs Settings access because it rewrites the project's brand. Research defaults to `lite` and is forced off when no domain is known. It PARKS for the user's approval like every agent generation here \u2014 release it with approve_ai_job \u2014 and `requestId` makes a retry return the first answer instead of a second page.",
+        z.object({
+          motion: z.enum(["new_account", "expand_customer", "accelerate_opportunity", "reengage_closed_lost"]),
+          context: z.string().min(20),
+          website: z.string().optional(),
+          name: z.string().optional(),
+          research: z.enum(["lite", "deep", "off"]).optional(),
+          ctaHref: z.string().optional(),
+          formId: z.string().optional(),
+          brandUrl: z.string().optional(),
+          requestId: z.string().optional()
+        }).shape,
+        async (c, a) => ok("Page queued for approval.", await data(c, "POST", `/management/campaigns/build`, {
+          motion: a.motion,
+          context: a.context,
+          website: a.website,
+          name: a.name,
+          research: a.research,
+          ctaHref: a.ctaHref,
+          formId: a.formId,
+          brandUrl: a.brandUrl,
+          requestId: a.requestId
+        }))
+      ),
       def(
         "claim_abm_task",
         "Claim an account to research",
@@ -4119,7 +4147,7 @@ ${res.warnings.join("\n")}` : summary, res.data);
       def(
         "get_deploy_status",
         "Get deploy/build status",
-        "Get the connected project's deploy/build status: state (idle|queued|building|failed), whether it's publishing, the live commit sha, when it went live, and any build error. Poll this after deploy_project until state is idle with your sha live. Also returns `canvas.lane` (the editor's live-preview lane for this site: `bridge` / `draft-route` / `none`) and `editorUrl`, the visual editor to hand the user.",
+        "Get the connected project's deploy/build status: state (idle|queued|building|categorizing|failed), whether it's publishing, the live commit sha, when it went live, and any build error. `categorizing` means the bytes are live but the import's setup lanes (content, pages, bindings) are still running, so `publishing` is still true and the site is not ready to edit yet. Poll this after deploy_project until state is idle with your sha live. Also returns `canvas.lane` (the editor's live-preview lane for this site: `bridge` / `draft-route` / `none`) and `editorUrl`, the visual editor to hand the user.",
         z.object({}).shape,
         async (c) => ok("Deploy status.", await data(c, "GET", `/management/projects/deploy-status`))
       )