brilliant-directories-mcp 6.58.607 → 6.58.608

package/index.js

@@ -327,7 +327,8 @@ async function _takenSlugsFor(config, slugs) {
 // front, and reused.
 // Mirrored in the Worker — keep in step.
 function aicSlugify(name) {
-  const ascii = String(name).toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(/^-+|-+$/g, "").slice(0, 60);
+  // Fold diacritics first: stripping them outright turns "Cafés" into "caf-s".
+  const ascii = String(name).normalize("NFD").replace(/[̀-ͯ]/g, "").toLowerCase().replace(/[^a-z0-9]+/g, "-").replace(/^-+|-+$/g, "").slice(0, 60);
   if (ascii) return ascii;
   // A name with no Latin characters percent-encodes, which is what BD itself stores
   // for sub-category slugs — a shared generic fallback would collide across every name.
@@ -400,8 +401,14 @@ async function buildCategoryTree(config, args) {
     return { status: "error", message: "Could not read the site's existing top categories; nothing was created. Retry." };
   }
   // Cross-namespace collision check for the tops we may have to create.
+  // Probe the suffix variants too: a collision is resolved by appending -1..-3, and those
+  // variants can themselves be taken by a web page, plan or member profile.
   const candidateSlugs = [];
-  for (const step of plan) if (idByName[step.top.toLowerCase()] === undefined) candidateSlugs.push(step.wantSlug || aicSlugify(step.top));
+  for (const step of plan) {
+    if (idByName[step.top.toLowerCase()] !== undefined) continue;
+    const base = step.wantSlug || aicSlugify(step.top);
+    candidateSlugs.push(base, base + "-1", base + "-2", base + "-3");
+  }
   if (candidateSlugs.length) {
     const foreign = await _takenSlugsFor(config, candidateSlugs);
     for (const k in foreign) takenSlugs[k] = true;
@@ -417,7 +424,11 @@ async function buildCategoryTree(config, args) {
     let slug = step.wantSlug || aicSlugify(step.top);
     if (takenSlugs[slug]) {
       let n = 1;
-      while (n <= 20 && takenSlugs[slug + "-" + n]) n++;
+      while (n <= 3 && takenSlugs[slug + "-" + n]) n++;
+      if (n > 3) {
+        results.push({ top_category: step.top, sub_categories: step.subs, top_status: "error", message: `the URL slug "${slug}" and its -1, -2 and -3 variants are all in use elsewhere on this site. Give this category a more distinct name, or pass a filename for it.` });
+        continue;
+      }
       slug = slug + "-" + n;
     }
     const resp = await makeRequest(config, "POST", "/api/v2/list_professions/create", null, { name: step.top, filename: slug });
@@ -491,6 +502,7 @@ async function buildCategoryTree(config, args) {
     message: {
       groups_requested: plan.length,
       groups_completed: results.length - failed.length,
+      sub_categories_created: results.reduce((n, r) => n + (r.sub_status === "created" ? r.sub_categories.length : 0), 0),
       temp_member: cleanup || (needSubs.length ? "no temporary member was created" : "not needed (no sub-categories requested)"),
       groups: results.map((r) => ({
         top_category: r.top_category,

package/openapi/bd-api.json

@@ -11752,7 +11752,7 @@
       "post": {
         "operationId": "createCategoryTree",
         "summary": "Create a full category taxonomy (tops + subs + sub-subs) in one call.",
-        "description": "Wrapper-native synthetic tool. Creates member categories — top categories, their sub-categories, and third-tier sub-sub-categories — in one call.\n\n**Use when:** creating a category at any level, including adding to a structure that already exists. Use `createTopCategory` or `createSubCategory` only for a single category that needs `desc`, `keywords`, `icon`, `sort_order`, `lead_price`, `image`, `master_id`, or a `filename` other than the default slug set at create time. For every other category create, use `createCategoryTree`.\n\n**Required:** `groups` — an array of `{ top_category, sub_categories }`, 25 entries maximum per call.\n\n**Send the whole taxonomy in one call.** A top category named again is matched by name and reused, so a later call adds to it. Never issue two calls concurrently: a top category named in both is created twice, because BD's category list does not reflect a row written by a call still in flight. A second call is safe once the first call's response has returned.\n\n**The three shapes, all the same input:**\n\n- New top plus its subs: `{ top_category: \"Surf Shops\", sub_categories: [\"Surfboards\", \"Wetsuits\"] }`\n\n- Subs under a top that already exists: the same shape, naming that top. It is reused; only the listed subs are added, and existing subs are left alone.\n\n- Top only: omit `sub_categories` or pass `[]`.\n\n**Third tier — `Parent=>Child`:** a `sub_categories` entry containing `=>` creates `Child` under `Parent`, and `Parent` under the group's `top_category`. An existing `Parent` is reused. Exactly one `=>` per entry: `\"Surf Camps=>Kids Camps\"`. `A=>B=>C` is rejected — send `A=>B` in this call, then `\"B=>C\"` in a second call naming the same `top_category` once this call's response has returned.\n\n**Sub-category names must not contain commas** — this tool writes them through BD's comma-separated `services` field, which would split one name into several. Replace the comma with a hyphen. To create the parts as separate categories instead, send each as its own `sub_categories` entry. One comma anywhere in `sub_categories` rejects the call. Top category names may contain commas.\n\n**Nothing is written until every name validates.** Writing itself is not atomic: a failure part-way leaves earlier groups created. `groups_completed` and each group's `top_status` / `sub_status` name exactly what landed — read them before retrying. Re-send a group only when its `top_status` is `error`, or its `sub_status` is `error` or `not attempted`; `created`, `existing`, and `none requested` all mean that part landed.\n\nBuilding sub-categories requires a temporary member, which this tool creates and deletes for you. `temp_member` reports what happened to it; the categories are unaffected either way.\n\n**See also:** `createTopCategory`, `createSubCategory`, `listTopCategories`, `listSubCategories`.\n\n**Returns:** `{ status, message: { groups_requested, groups_completed, temp_member, groups: [{ top_category, profession_id, top_status, sub_categories, sub_status }] } }`. `top_status` is `created`, `existing`, or `error`. `sub_status` is `created`, `error`, `none requested`, or `not attempted`. `temp_member` is one of: `temporary member deleted` — cleanup succeeded; `not needed (no sub-categories requested)`; `no temporary member was created` — no sub-category was written and every `sub_status` is `error`; or a `user_id` — sub-categories were written but cleanup failed, so pass that id to `deleteUser`. Each group carries the resolved `profession_id`, ready for `updateUser.profession_id`. Sub-category ids are not returned — read them with `listSubCategories` filtered on that `profession_id` before assigning members via `updateUser.services` or `createMemberSubCategoryLink`.",
+        "description": "Wrapper-native synthetic tool. Creates member categories — top categories, their sub-categories, and third-tier sub-sub-categories — in one call.\n\n**Use when:** creating a category at any level, including adding to a structure that already exists. Use `createTopCategory` or `createSubCategory` only for a single category that needs `desc`, `keywords`, `icon`, `sort_order`, `lead_price`, `image`, `master_id`, or a `filename` other than the default slug set at create time. For every other category create, use `createCategoryTree`.\n\n**Required:** `groups` — an array of `{ top_category, sub_categories }`, 25 entries maximum per call.\n\n**Send the whole taxonomy in one call.** A top category named again is matched by name and reused, so a later call adds to it. Never issue two calls concurrently: a top category named in both is created twice, because BD's category list does not reflect a row written by a call still in flight. A second call is safe once the first call's response has returned.\n\n**The three shapes, all the same input:**\n\n- New top plus its subs: `{ top_category: \"Surf Shops\", sub_categories: [\"Surfboards\", \"Wetsuits\"] }`\n\n- Subs under a top that already exists: the same shape, naming that top. It is reused; only the listed subs are added, and existing subs are left alone.\n\n- Top only: omit `sub_categories` or pass `[]`.\n\n**Third tier — `Parent=>Child`:** a `sub_categories` entry containing `=>` creates `Child` under `Parent`, and `Parent` under the group's `top_category`. An existing `Parent` is reused. Exactly one `=>` per entry: `\"Surf Camps=>Kids Camps\"`. `A=>B=>C` is rejected — send `A=>B` in this call, then `\"B=>C\"` in a second call naming the same `top_category` once this call's response has returned.\n\n**Sub-category names must not contain commas** — this tool writes them through BD's comma-separated `services` field, which would split one name into several. Replace the comma with a hyphen. To create the parts as separate categories instead, send each as its own `sub_categories` entry. One comma anywhere in `sub_categories` rejects the call. Top category names may contain commas.\n\n**Nothing is written until every name validates.** Writing itself is not atomic: a failure part-way leaves earlier groups created. `groups_completed` and each group's `top_status` / `sub_status` name exactly what landed — read them before retrying. Re-send a group only when its `top_status` is `error`, or its `sub_status` is `error` or `not attempted`; `created`, `existing`, and `none requested` all mean that part landed.\n\nBuilding sub-categories requires a temporary member, which this tool creates and deletes for you. `temp_member` reports what happened to it; the categories are unaffected either way.\n\n**See also:** `createTopCategory`, `createSubCategory`, `listTopCategories`, `listSubCategories`.\n\n**Returns:** `{ status, message: { groups_requested, groups_completed, sub_categories_created, temp_member, groups: [{ top_category, profession_id, top_status, sub_categories, sub_status }] } }`. `top_status` is `created`, `existing`, or `error`. `sub_status` is `created`, `error`, `none requested`, or `not attempted`. `sub_categories_created` is the total across all groups — report it rather than counting names. `temp_member` is one of: `temporary member deleted` — cleanup succeeded; `not needed (no sub-categories requested)`; `no temporary member was created` — no sub-category was written and every `sub_status` is `error`; or a `user_id` — sub-categories were written but cleanup failed, so pass that id to `deleteUser`. Each group carries the resolved `profession_id`, ready for `updateUser.profession_id`. Sub-category ids are not returned — read them with `listSubCategories` filtered on that `profession_id` before assigning members via `updateUser.services` or `createMemberSubCategoryLink`.",
         "tags": [
           "Categories"
         ],

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "brilliant-directories-mcp",
   "mcpName": "io.github.brilliantdirectories/brilliant-directories-mcp",
-  "version": "6.58.607",
+  "version": "6.58.608",
   "description": "Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.",
   "main": "index.js",
   "bin": {