brilliant-directories-mcp 2.0.0 → 3.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/openapi/bd-api.json +260 -234
- package/package.json +1 -1
package/openapi/bd-api.json
CHANGED
|
@@ -1862,7 +1862,7 @@
|
|
|
1862
1862
|
"post": {
|
|
1863
1863
|
"operationId": "searchUsers",
|
|
1864
1864
|
"summary": "Search members/users",
|
|
1865
|
-
"description": "Full-text search across members with category, location, and sorting options.\n\n**Pagination:** cursor-based. Pass `limit` (default 25, max 100) and `page` to paginate large result sets.\n\n**Enums:** `sort`: `reviews`, `name ASC`, `name DESC`, `last_name_asc`, `last_name_desc`.\n\n**Parameter interactions:**\n- `q` — keyword (matches first name, last name, company, about, search_description)\n- `pid` (category ID), `tid` (sub-category/service ID), `ttid` (sub-sub-category) — taxonomy filters, use IDs from `
|
|
1865
|
+
"description": "Full-text search across members with category, location, and sorting options.\n\n**Pagination:** cursor-based. Pass `limit` (default 25, max 100) and `page` to paginate large result sets.\n\n**Enums:** `sort`: `reviews`, `name ASC`, `name DESC`, `last_name_asc`, `last_name_desc`.\n\n**Parameter interactions:**\n- `q` — keyword (matches first name, last name, company, about, search_description)\n- `pid` (category ID), `tid` (sub-category/service ID), `ttid` (sub-sub-category) — taxonomy filters, use IDs from `listTopCategories` / `listSubCategories`\n- `address` + `dynamic=1` — proximity/geographic filtering\n- `output_type=html` returns server-rendered HTML; `array` (default) returns structured JSON\n\n**See also:** `getUser` (single record by ID), `listUsers` (full enumeration).\n\n**Returns:** `{ status: \"success\", message: [...records] }`. Supports pagination fields when result set is large.\n\n**Profile URL:** every user record has a `filename` field. To get the full public profile URL, concatenate: `<site-domain>/<user.filename>`. The `filename` is the complete relative path (e.g., `united-states/monterey-park/doctor/harrison-hasanuddin-d-o`) — DO NOT prepend `/business/`, `/profile/`, `/member/`, or any other segment. BD's router resolves `filename` verbatim.\n\n",
|
|
1866
1866
|
"tags": [
|
|
1867
1867
|
"Users"
|
|
1868
1868
|
],
|
|
@@ -2706,7 +2706,7 @@
|
|
|
2706
2706
|
}
|
|
2707
2707
|
}
|
|
2708
2708
|
},
|
|
2709
|
-
"description": "Create a new lead record. Writes live data.\n\n**Required:** `lead_name`, `lead_email`, `lead_phone`, `lead_message`, `lead_location`, `top_id`.\n\n**Parameter interactions:**\n- `top_id` — category ID; discover via `
|
|
2709
|
+
"description": "Create a new lead record. Writes live data.\n\n**Required:** `lead_name`, `lead_email`, `lead_phone`, `lead_message`, `lead_location`, `top_id`.\n\n**Parameter interactions:**\n- `top_id` — category ID; discover via `listTopCategories`\n- All 6 required fields (`lead_name`, `lead_email`, `lead_phone`, `lead_message`, `lead_location`, `top_id`) must be supplied together\n- Response includes `lead_id` AND `token` — token may be needed for customer-facing URLs\n- After creating, call `matchLead` to trigger member notifications\n\n**See also:** `updateLead` (modify existing).\n\n**Writes live data:** confirm intent with the user for bulk operations. Changes are immediately visible on the live site.\n\n**Returns:** `{ status: \"success\", message: {...createdRecord} }` — includes the server-assigned ID (e.g., `user_id`, `post_id`). Use this ID for follow-up operations.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
2710
2710
|
}
|
|
2711
2711
|
},
|
|
2712
2712
|
"/api/v2/leads/match": {
|
|
@@ -6121,221 +6121,9 @@
|
|
|
6121
6121
|
"description": "Permanently delete a menuitem record by ID. Destructive — cannot be undone via API.\n\n**Required:** `menu_item_id`.\n\n**See also:** `updateMenuItem` (modify without removing).\n\n**Destructive:** confirm intent with the user before bulk use. No soft-delete via API — records removed are not recoverable.\n\n**Returns:** `{ status: \"success\", message: \"record was deleted\" }`. No body beyond the confirmation string.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6122
6122
|
}
|
|
6123
6123
|
},
|
|
6124
|
-
"/api/v2/category/get": {
|
|
6125
|
-
"get": {
|
|
6126
|
-
"operationId": "listCategories",
|
|
6127
|
-
"summary": "List categories (professions)",
|
|
6128
|
-
"tags": [
|
|
6129
|
-
"Categories"
|
|
6130
|
-
],
|
|
6131
|
-
"parameters": [
|
|
6132
|
-
{
|
|
6133
|
-
"$ref": "#/components/parameters/limit"
|
|
6134
|
-
},
|
|
6135
|
-
{
|
|
6136
|
-
"$ref": "#/components/parameters/page"
|
|
6137
|
-
}
|
|
6138
|
-
],
|
|
6139
|
-
"responses": {
|
|
6140
|
-
"200": {
|
|
6141
|
-
"description": "Paginated category list",
|
|
6142
|
-
"content": {
|
|
6143
|
-
"application/json": {
|
|
6144
|
-
"schema": {
|
|
6145
|
-
"$ref": "#/components/schemas/PaginatedResponse"
|
|
6146
|
-
}
|
|
6147
|
-
}
|
|
6148
|
-
}
|
|
6149
|
-
}
|
|
6150
|
-
},
|
|
6151
|
-
"description": "Paginated enumeration of category records. Read-only.\n\n**Pagination:** cursor-based. Pass `limit` (default 25, max 100) and `page` token from the previous response's `next_page`. Do not assume integer offsets.\n\n**Filter/sort:** `property` + `property_value` + `property_operator` (`=`, `LIKE`, `>`, `<`, `>=`, `<=`) to filter; `order_column` + `order_type` (`ASC`/`DESC`) to sort.\n\n**See also:** `getCategory` (single record by ID).\n\n**Returns:** `{ status: \"success\", total, current_page, total_pages, next_page, prev_page, message: [...records] }`. Each record is the full resource object.\n\n**BD taxonomy model:** Returns TOP-LEVEL categories (BD's \"professions\"), NOT sub-categories. For sub-categories under a specific category, use `listServices` filtered by `profession_id`. Each returned record's `category_id` is what populates a user's `profession_id` field.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6152
|
-
}
|
|
6153
|
-
},
|
|
6154
|
-
"/api/v2/category/get/{category_id}": {
|
|
6155
|
-
"get": {
|
|
6156
|
-
"operationId": "getCategory",
|
|
6157
|
-
"summary": "Get a single category",
|
|
6158
|
-
"tags": [
|
|
6159
|
-
"Categories"
|
|
6160
|
-
],
|
|
6161
|
-
"parameters": [
|
|
6162
|
-
{
|
|
6163
|
-
"name": "category_id",
|
|
6164
|
-
"in": "path",
|
|
6165
|
-
"required": true,
|
|
6166
|
-
"schema": {
|
|
6167
|
-
"type": "integer"
|
|
6168
|
-
}
|
|
6169
|
-
}
|
|
6170
|
-
],
|
|
6171
|
-
"responses": {
|
|
6172
|
-
"200": {
|
|
6173
|
-
"description": "Category record",
|
|
6174
|
-
"content": {
|
|
6175
|
-
"application/json": {
|
|
6176
|
-
"schema": {
|
|
6177
|
-
"$ref": "#/components/schemas/SuccessResponse"
|
|
6178
|
-
}
|
|
6179
|
-
}
|
|
6180
|
-
}
|
|
6181
|
-
}
|
|
6182
|
-
},
|
|
6183
|
-
"description": "Fetch a single category record. Read-only.\n\n**Required:** `category_id`.\n\n**See also:** `listCategories` (enumerate many).\n\n**Returns:** `{ status: \"success\", message: [{...record}] }` — the `message` array contains 1 record when found. Empty or HTTP 404 when not found.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6184
|
-
}
|
|
6185
|
-
},
|
|
6186
|
-
"/api/v2/category/create": {
|
|
6187
|
-
"post": {
|
|
6188
|
-
"operationId": "createCategory",
|
|
6189
|
-
"summary": "Create a category",
|
|
6190
|
-
"tags": [
|
|
6191
|
-
"Categories"
|
|
6192
|
-
],
|
|
6193
|
-
"requestBody": {
|
|
6194
|
-
"required": true,
|
|
6195
|
-
"content": {
|
|
6196
|
-
"application/x-www-form-urlencoded": {
|
|
6197
|
-
"schema": {
|
|
6198
|
-
"type": "object",
|
|
6199
|
-
"required": [
|
|
6200
|
-
"name",
|
|
6201
|
-
"filename",
|
|
6202
|
-
"group_id"
|
|
6203
|
-
],
|
|
6204
|
-
"properties": {
|
|
6205
|
-
"name": {
|
|
6206
|
-
"type": "string"
|
|
6207
|
-
},
|
|
6208
|
-
"filename": {
|
|
6209
|
-
"type": "string",
|
|
6210
|
-
"description": "URL-friendly slug"
|
|
6211
|
-
},
|
|
6212
|
-
"group_id": {
|
|
6213
|
-
"type": "integer"
|
|
6214
|
-
},
|
|
6215
|
-
"keywords": {
|
|
6216
|
-
"type": "string"
|
|
6217
|
-
},
|
|
6218
|
-
"icon": {
|
|
6219
|
-
"type": "string"
|
|
6220
|
-
}
|
|
6221
|
-
}
|
|
6222
|
-
}
|
|
6223
|
-
}
|
|
6224
|
-
}
|
|
6225
|
-
},
|
|
6226
|
-
"responses": {
|
|
6227
|
-
"200": {
|
|
6228
|
-
"description": "Category created",
|
|
6229
|
-
"content": {
|
|
6230
|
-
"application/json": {
|
|
6231
|
-
"schema": {
|
|
6232
|
-
"$ref": "#/components/schemas/SuccessResponse"
|
|
6233
|
-
}
|
|
6234
|
-
}
|
|
6235
|
-
}
|
|
6236
|
-
}
|
|
6237
|
-
},
|
|
6238
|
-
"description": "Create a new category record. Writes live data.\n\n**Required:** `name`, `filename`, `group_id`.\n\n**Parameter interactions:**\n- `name` — human-readable category name (e.g. \"Restaurants\")\n- `filename` — URL-slug form of the name (e.g. \"restaurants\")\n- `group_id` — integer; most BD sites use `group_id=1` by default\n\n**See also:** `updateCategory` (modify existing), `deleteCategory` (remove).\n\n**Writes live data:** confirm intent with the user for bulk operations. Changes are immediately visible on the live site.\n\n**Returns:** `{ status: \"success\", message: {...createdRecord} }` — includes the server-assigned ID. Use the returned `category_id` to populate user records' `profession_id` field.\n\n**BD taxonomy model:** This creates a TOP-LEVEL category (internally called a \"profession\"). It populates the `profession_id` field on user records. To create sub-classifications under this category, use `createService` after (passing this category's ID as `profession_id`). The 2-tier model: Category (this) → Service. There is NO `createProfession` tool — `createCategory` IS the profession-creator.\n\n**Common workflow — fresh taxonomy setup (\"create Restaurants with Sushi sub-category, assign Alice\"):**\n\n1. `createCategory` with `name=\"Restaurants\"`, `filename=\"restaurants\"`, `group_id=1` → returns `category_id` (e.g. 42). This is what populates a user's `profession_id`.\n2. `createService` with `name=\"Sushi\"`, `profession_id=42`, `filename=\"sushi\"` → returns `service_id` (e.g. 17).\n3. Assign Alice: `updateUser` with `user_id=<Alice>`, `profession_id=42`, `services=\"17\"`. (For per-service pricing/specialty, use `createUserService` instead.)\n\nDo NOT look for a `createProfession` tool — it doesn't exist. `createCategory` IS the profession-creator.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6239
|
-
}
|
|
6240
|
-
},
|
|
6241
|
-
"/api/v2/category/update": {
|
|
6242
|
-
"put": {
|
|
6243
|
-
"operationId": "updateCategory",
|
|
6244
|
-
"summary": "Update a category",
|
|
6245
|
-
"tags": [
|
|
6246
|
-
"Categories"
|
|
6247
|
-
],
|
|
6248
|
-
"requestBody": {
|
|
6249
|
-
"required": true,
|
|
6250
|
-
"content": {
|
|
6251
|
-
"application/x-www-form-urlencoded": {
|
|
6252
|
-
"schema": {
|
|
6253
|
-
"type": "object",
|
|
6254
|
-
"required": [
|
|
6255
|
-
"category_id"
|
|
6256
|
-
],
|
|
6257
|
-
"properties": {
|
|
6258
|
-
"category_id": {
|
|
6259
|
-
"type": "integer"
|
|
6260
|
-
},
|
|
6261
|
-
"name": {
|
|
6262
|
-
"type": "string"
|
|
6263
|
-
},
|
|
6264
|
-
"filename": {
|
|
6265
|
-
"type": "string"
|
|
6266
|
-
},
|
|
6267
|
-
"group_id": {
|
|
6268
|
-
"type": "integer"
|
|
6269
|
-
},
|
|
6270
|
-
"keywords": {
|
|
6271
|
-
"type": "string"
|
|
6272
|
-
},
|
|
6273
|
-
"icon": {
|
|
6274
|
-
"type": "string"
|
|
6275
|
-
}
|
|
6276
|
-
}
|
|
6277
|
-
}
|
|
6278
|
-
}
|
|
6279
|
-
}
|
|
6280
|
-
},
|
|
6281
|
-
"responses": {
|
|
6282
|
-
"200": {
|
|
6283
|
-
"description": "Category updated",
|
|
6284
|
-
"content": {
|
|
6285
|
-
"application/json": {
|
|
6286
|
-
"schema": {
|
|
6287
|
-
"$ref": "#/components/schemas/SuccessResponse"
|
|
6288
|
-
}
|
|
6289
|
-
}
|
|
6290
|
-
}
|
|
6291
|
-
}
|
|
6292
|
-
},
|
|
6293
|
-
"description": "Update an existing category record by ID. Fields omitted are untouched. Writes live data.\n\n**Required:** `category_id`.\n\n**See also:** `createCategory` (add new), `deleteCategory` (remove permanently).\n\n**Writes live data:** confirm intent with the user for bulk operations. Changes are immediately visible on the live site.\n\n**Returns:** `{ status: \"success\", message: {...updatedRecord} }` — the full updated record after changes applied.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6294
|
-
}
|
|
6295
|
-
},
|
|
6296
|
-
"/api/v2/category/delete": {
|
|
6297
|
-
"delete": {
|
|
6298
|
-
"operationId": "deleteCategory",
|
|
6299
|
-
"summary": "Delete a category",
|
|
6300
|
-
"tags": [
|
|
6301
|
-
"Categories"
|
|
6302
|
-
],
|
|
6303
|
-
"requestBody": {
|
|
6304
|
-
"required": true,
|
|
6305
|
-
"content": {
|
|
6306
|
-
"application/x-www-form-urlencoded": {
|
|
6307
|
-
"schema": {
|
|
6308
|
-
"type": "object",
|
|
6309
|
-
"required": [
|
|
6310
|
-
"category_id"
|
|
6311
|
-
],
|
|
6312
|
-
"properties": {
|
|
6313
|
-
"category_id": {
|
|
6314
|
-
"type": "integer"
|
|
6315
|
-
}
|
|
6316
|
-
}
|
|
6317
|
-
}
|
|
6318
|
-
}
|
|
6319
|
-
}
|
|
6320
|
-
},
|
|
6321
|
-
"responses": {
|
|
6322
|
-
"200": {
|
|
6323
|
-
"description": "Category deleted",
|
|
6324
|
-
"content": {
|
|
6325
|
-
"application/json": {
|
|
6326
|
-
"schema": {
|
|
6327
|
-
"$ref": "#/components/schemas/DeleteResponse"
|
|
6328
|
-
}
|
|
6329
|
-
}
|
|
6330
|
-
}
|
|
6331
|
-
}
|
|
6332
|
-
},
|
|
6333
|
-
"description": "Permanently delete a category record by ID. Destructive — cannot be undone via API.\n\n**Required:** `category_id`.\n\n**See also:** `updateCategory` (modify without removing).\n\n**Destructive:** confirm intent with the user before bulk use. No soft-delete via API — records removed are not recoverable.\n\n**Returns:** `{ status: \"success\", message: \"record was deleted\" }`. No body beyond the confirmation string.\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6334
|
-
}
|
|
6335
|
-
},
|
|
6336
6124
|
"/api/v2/list_services/get": {
|
|
6337
6125
|
"get": {
|
|
6338
|
-
"operationId": "
|
|
6126
|
+
"operationId": "listSubCategories",
|
|
6339
6127
|
"summary": "List services (sub-categories)",
|
|
6340
6128
|
"tags": [
|
|
6341
6129
|
"Services"
|
|
@@ -6360,12 +6148,12 @@
|
|
|
6360
6148
|
}
|
|
6361
6149
|
}
|
|
6362
6150
|
},
|
|
6363
|
-
"description": "Paginated enumeration of
|
|
6151
|
+
"description": "Paginated enumeration of SUB-level member categories (services). Read-only.\n\nSub Categories are level 2 of the 3-tier member classification (e.g., \"Sushi\" under \"Restaurants\"). Each has a `profession_id` pointing at its parent Top Category. `master_id` points at a parent Sub Category for sub-sub-category nesting (`master_id=0` = directly under a Top Category). Backed by BD's `list_services` table.\n\n**Pagination:** cursor-based. Pass `limit` (default 25, max 100) and `page` token.\n\n**Filter/sort:** filter by `profession_id` to scope to sub-categories under one top category. Standard `property`/`property_value`/`property_operator` for other fields.\n\n**See also:** `getSubCategory` (single by ID), `listTopCategories` (parents), `createSubCategory` (add new).\n\n**Returns:** `{ status: \"success\", total, ..., message: [...records] }`. Each record has `service_id`, `name`, `desc`, `profession_id`, `master_id`, `filename`, `keywords`, `sort_order`, `lead_price`, `image`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6364
6152
|
}
|
|
6365
6153
|
},
|
|
6366
6154
|
"/api/v2/list_services/get/{service_id}": {
|
|
6367
6155
|
"get": {
|
|
6368
|
-
"operationId": "
|
|
6156
|
+
"operationId": "getSubCategory",
|
|
6369
6157
|
"summary": "Get a single service",
|
|
6370
6158
|
"tags": [
|
|
6371
6159
|
"Services"
|
|
@@ -6392,12 +6180,12 @@
|
|
|
6392
6180
|
}
|
|
6393
6181
|
}
|
|
6394
6182
|
},
|
|
6395
|
-
"description": "Fetch a single service
|
|
6183
|
+
"description": "Fetch a single SUB-level member category (service) by `service_id`. Read-only.\n\n**Required:** `service_id` (path).\n\n**See also:** `listSubCategories` (enumerate; filter by `profession_id` for scope), `getTopCategory` (fetch parent Top by `profession_id`).\n\n**Returns:** `{ status: \"success\", message: [{...record}] }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6396
6184
|
}
|
|
6397
6185
|
},
|
|
6398
6186
|
"/api/v2/list_services/create": {
|
|
6399
6187
|
"post": {
|
|
6400
|
-
"operationId": "
|
|
6188
|
+
"operationId": "createSubCategory",
|
|
6401
6189
|
"summary": "Create a service",
|
|
6402
6190
|
"tags": [
|
|
6403
6191
|
"Services"
|
|
@@ -6455,12 +6243,12 @@
|
|
|
6455
6243
|
}
|
|
6456
6244
|
}
|
|
6457
6245
|
},
|
|
6458
|
-
"description": "Create a new
|
|
6246
|
+
"description": "Create a new SUB-level member category under an existing Top Category. Writes live data.\n\nA Sub Category is level 2 of the 3-tier member classification. It MUST have a parent Top Category (via `profession_id`). It may optionally sit under another Sub Category (for sub-sub-category nesting, via `master_id`). Backed by BD's `list_services` table.\n\n**Required:** `name`, `profession_id`.\n\n**Parameter guidance:**\n- `name` — human-readable (e.g. \"Sushi\")\n- `profession_id` — the parent Top Category's ID (from `listTopCategories` or `createTopCategory`)\n- `master_id` — for SUB-SUB-CATEGORY nesting, pass the parent Sub Category's ID; default 0 means \"directly under the Top Category\"\n- `filename` — URL-slug form; `desc`, `keywords`, `sort_order`, `lead_price`, `image` — all optional\n\n**See also:** `updateSubCategory` (modify), `listSubCategories` (list), `createTopCategory` (create parent).\n\n**Writes live data:** changes are immediately visible on the public site.\n\n**Returns:** `{ status: \"success\", message: {...createdRecord} }` including `service_id`. Use that to assign members via `updateUser.services` (CSV) or `createMemberSubCategoryLink`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6459
6247
|
}
|
|
6460
6248
|
},
|
|
6461
6249
|
"/api/v2/list_services/update": {
|
|
6462
6250
|
"put": {
|
|
6463
|
-
"operationId": "
|
|
6251
|
+
"operationId": "updateSubCategory",
|
|
6464
6252
|
"summary": "Update a service",
|
|
6465
6253
|
"tags": [
|
|
6466
6254
|
"Services"
|
|
@@ -6519,12 +6307,12 @@
|
|
|
6519
6307
|
}
|
|
6520
6308
|
}
|
|
6521
6309
|
},
|
|
6522
|
-
"description": "Update an existing
|
|
6310
|
+
"description": "Update an existing SUB-level member category by `service_id`. Fields omitted are untouched. Writes live data.\n\n**Required:** `service_id`.\n\n**Parameter notes:**\n- Change `profession_id` to move this Sub Category to a different parent Top Category\n- Change `master_id` to re-nest as a sub-sub-category (non-zero) or flatten to direct-under-Top (0)\n\n**See also:** `createSubCategory` (add new), `deleteSubCategory` (remove).\n\n**Returns:** `{ status: \"success\", message: {...updatedRecord} }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6523
6311
|
}
|
|
6524
6312
|
},
|
|
6525
6313
|
"/api/v2/list_services/delete": {
|
|
6526
6314
|
"delete": {
|
|
6527
|
-
"operationId": "
|
|
6315
|
+
"operationId": "deleteSubCategory",
|
|
6528
6316
|
"summary": "Delete a service",
|
|
6529
6317
|
"tags": [
|
|
6530
6318
|
"Services"
|
|
@@ -6559,12 +6347,12 @@
|
|
|
6559
6347
|
}
|
|
6560
6348
|
}
|
|
6561
6349
|
},
|
|
6562
|
-
"description": "Permanently delete a
|
|
6350
|
+
"description": "Permanently delete a SUB-level member category by `service_id`. Destructive — cannot be undone via API.\n\n**Required:** `service_id`.\n\n**Destructive:** confirm intent. Members whose `users_data.services` CSV contains this ID will have an orphan reference. Any Member ↔ Sub Category links (`rel_services`) pointing at this service_id also become orphaned.\n\n**See also:** `updateSubCategory` (modify without removing).\n\n**Returns:** `{ status: \"success\", message: \"list_services record was deleted\" }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6563
6351
|
}
|
|
6564
6352
|
},
|
|
6565
6353
|
"/api/v2/rel_services/get": {
|
|
6566
6354
|
"get": {
|
|
6567
|
-
"operationId": "
|
|
6355
|
+
"operationId": "listMemberSubCategoryLinks",
|
|
6568
6356
|
"summary": "List user-service relationships",
|
|
6569
6357
|
"tags": [
|
|
6570
6358
|
"User Services"
|
|
@@ -6589,12 +6377,12 @@
|
|
|
6589
6377
|
}
|
|
6590
6378
|
}
|
|
6591
6379
|
},
|
|
6592
|
-
"description": "Paginated enumeration of
|
|
6380
|
+
"description": "Paginated enumeration of MEMBER ↔ SUB CATEGORY links. Read-only.\n\nEach record links a member (`user_id`) to a Sub Category (`service_id`) with per-link metadata: `avg_price`, `specialty`, `num_completed`, `date`. This is level 3 of the member-taxonomy relationship. Backed by BD's `rel_services` table.\n\n**When to use this vs. the simpler `users_data.services` CSV field:** use this resource when you need PER-LINK metadata (pricing tier, specialty flag, completion counter). If you just want \"this member is tagged with these Sub Categories\" with no extra data, set `updateUser.services` (CSV of service IDs) instead.\n\n**Pagination + filter/sort:** standard.\n\n**See also:** `getMemberSubCategoryLink`, `createMemberSubCategoryLink`, `listSubCategories` (available Sub Categories), `updateUser` (sets the `services` CSV for simpler cases).\n\n**Returns:** `{ status: \"success\", ..., message: [...records] }`. Each has `rel_id`, `user_id`, `service_id`, `date`, `avg_price`, `num_completed`, `specialty`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6593
6381
|
}
|
|
6594
6382
|
},
|
|
6595
6383
|
"/api/v2/rel_services/get/{rel_id}": {
|
|
6596
6384
|
"get": {
|
|
6597
|
-
"operationId": "
|
|
6385
|
+
"operationId": "getMemberSubCategoryLink",
|
|
6598
6386
|
"summary": "Get a single user-service relationship",
|
|
6599
6387
|
"tags": [
|
|
6600
6388
|
"User Services"
|
|
@@ -6621,12 +6409,12 @@
|
|
|
6621
6409
|
}
|
|
6622
6410
|
}
|
|
6623
6411
|
},
|
|
6624
|
-
"description": "Fetch a single
|
|
6412
|
+
"description": "Fetch a single Member ↔ Sub Category link by `rel_id`. Read-only.\n\n**Required:** `rel_id`.\n\n**See also:** `listMemberSubCategoryLinks` (enumerate, filter by `user_id` or `service_id`).\n\n**Returns:** `{ status: \"success\", message: [{...record}] }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6625
6413
|
}
|
|
6626
6414
|
},
|
|
6627
6415
|
"/api/v2/rel_services/create": {
|
|
6628
6416
|
"post": {
|
|
6629
|
-
"operationId": "
|
|
6417
|
+
"operationId": "createMemberSubCategoryLink",
|
|
6630
6418
|
"summary": "Link a service to a user",
|
|
6631
6419
|
"tags": [
|
|
6632
6420
|
"User Services"
|
|
@@ -6679,12 +6467,12 @@
|
|
|
6679
6467
|
}
|
|
6680
6468
|
}
|
|
6681
6469
|
},
|
|
6682
|
-
"description": "Create a new
|
|
6470
|
+
"description": "Create a new Member ↔ Sub Category link with optional metadata. Writes live data.\n\nLinks an existing member (`user_id`) to an existing Sub Category (`service_id`) with per-link metadata (pricing, specialty). This is the richer alternative to setting `users_data.services` CSV via `updateUser` — use this when you need per-link data.\n\n**Required:** `user_id`, `service_id`.\n\n**Parameter guidance:**\n- `user_id` — member (from `listUsers` / `searchUsers`)\n- `service_id` — Sub Category (from `listSubCategories`)\n- `avg_price` — decimal, the member's price for this service\n- `specialty` — `0` or `1` flags this Sub Category as a specialty offering on the member's profile\n- `num_completed` — counter of jobs/projects completed in this Sub Category\n- `date` — YYYYMMDDHHmmss timestamp\n\n**See also:** `updateUser` with `services=\"<csv>\"` (simpler, no per-link metadata), `listSubCategories`, `getMemberSubCategoryLink`.\n\n**Writes live data:** appears on the member's public profile immediately.\n\n**Returns:** `{ status: \"success\", message: {...createdRecord} }` with `rel_id`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6683
6471
|
}
|
|
6684
6472
|
},
|
|
6685
6473
|
"/api/v2/rel_services/update": {
|
|
6686
6474
|
"put": {
|
|
6687
|
-
"operationId": "
|
|
6475
|
+
"operationId": "updateMemberSubCategoryLink",
|
|
6688
6476
|
"summary": "Update a user-service relationship",
|
|
6689
6477
|
"tags": [
|
|
6690
6478
|
"User Services"
|
|
@@ -6731,12 +6519,12 @@
|
|
|
6731
6519
|
}
|
|
6732
6520
|
}
|
|
6733
6521
|
},
|
|
6734
|
-
"description": "Update
|
|
6522
|
+
"description": "Update a Member ↔ Sub Category link by `rel_id`. Fields omitted are untouched. Writes live data.\n\n**Required:** `rel_id`.\n\n**Updatable fields:** `avg_price`, `specialty`, `num_completed`, `date`.\n\n**See also:** `createMemberSubCategoryLink` (add new), `deleteMemberSubCategoryLink` (remove).\n\n**Returns:** `{ status: \"success\", message: {...updatedRecord} }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6735
6523
|
}
|
|
6736
6524
|
},
|
|
6737
6525
|
"/api/v2/rel_services/delete": {
|
|
6738
6526
|
"delete": {
|
|
6739
|
-
"operationId": "
|
|
6527
|
+
"operationId": "deleteMemberSubCategoryLink",
|
|
6740
6528
|
"summary": "Remove a service from a user",
|
|
6741
6529
|
"tags": [
|
|
6742
6530
|
"User Services"
|
|
@@ -6771,7 +6559,7 @@
|
|
|
6771
6559
|
}
|
|
6772
6560
|
}
|
|
6773
6561
|
},
|
|
6774
|
-
"description": "Permanently delete a
|
|
6562
|
+
"description": "Permanently delete a Member ↔ Sub Category link by `rel_id`. Destructive — cannot be undone via API.\n\nRemoves the member's link to this Sub Category in the `rel_services` join table. Does NOT remove the member from `users_data.services` CSV if the service_id is listed there — update that separately via `updateUser` if needed.\n\n**Required:** `rel_id`.\n\n**Returns:** `{ status: \"success\", message: \"rel_services record was deleted\" }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
6775
6563
|
}
|
|
6776
6564
|
},
|
|
6777
6565
|
"/api/v2/users_photo/get": {
|
|
@@ -9275,6 +9063,244 @@
|
|
|
9275
9063
|
}
|
|
9276
9064
|
}
|
|
9277
9065
|
}
|
|
9066
|
+
},
|
|
9067
|
+
"/api/v2/list_professions/get": {
|
|
9068
|
+
"get": {
|
|
9069
|
+
"operationId": "listTopCategories",
|
|
9070
|
+
"summary": "List categories (professions)",
|
|
9071
|
+
"tags": [
|
|
9072
|
+
"Categories"
|
|
9073
|
+
],
|
|
9074
|
+
"parameters": [
|
|
9075
|
+
{
|
|
9076
|
+
"$ref": "#/components/parameters/limit"
|
|
9077
|
+
},
|
|
9078
|
+
{
|
|
9079
|
+
"$ref": "#/components/parameters/page"
|
|
9080
|
+
}
|
|
9081
|
+
],
|
|
9082
|
+
"responses": {
|
|
9083
|
+
"200": {
|
|
9084
|
+
"description": "Paginated category list",
|
|
9085
|
+
"content": {
|
|
9086
|
+
"application/json": {
|
|
9087
|
+
"schema": {
|
|
9088
|
+
"$ref": "#/components/schemas/PaginatedResponse"
|
|
9089
|
+
}
|
|
9090
|
+
}
|
|
9091
|
+
}
|
|
9092
|
+
}
|
|
9093
|
+
},
|
|
9094
|
+
"description": "Paginated enumeration of TOP-level member categories. Read-only.\n\nTop Categories are the highest level of the 3-tier member classification (e.g., \"Restaurants\", \"Dentists\"). Each record's `profession_id` is what populates `users_data.profession_id` on member records. Backed by BD's `list_professions` table.\n\n**Pagination:** cursor-based. Pass `limit` (default 25, max 100) and `page` token from the previous response's `next_page`. Do not assume integer offsets.\n\n**Filter/sort:** `property` + `property_value` + `property_operator` (`=`, `LIKE`, `>`, `<`, `>=`, `<=`) to filter; `order_column` + `order_type` (`ASC`/`DESC`) to sort.\n\n**See also:** `getTopCategory` (single by ID), `listSubCategories` (sub-categories filtered by `profession_id`), `createTopCategory` (add new).\n\n**Returns:** `{ status: \"success\", total, current_page, total_pages, next_page, prev_page, message: [...records] }`. Each record has `profession_id`, `name`, `desc`, `filename`, `keywords`, `icon`, `sort_order`, `lead_price`, `image`, `revision_timestamp`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
9095
|
+
}
|
|
9096
|
+
},
|
|
9097
|
+
"/api/v2/list_professions/get/{profession_id}": {
|
|
9098
|
+
"get": {
|
|
9099
|
+
"operationId": "getTopCategory",
|
|
9100
|
+
"summary": "Get a single category",
|
|
9101
|
+
"tags": [
|
|
9102
|
+
"Categories"
|
|
9103
|
+
],
|
|
9104
|
+
"parameters": [
|
|
9105
|
+
{
|
|
9106
|
+
"name": "profession_id",
|
|
9107
|
+
"in": "path",
|
|
9108
|
+
"required": true,
|
|
9109
|
+
"schema": {
|
|
9110
|
+
"type": "integer"
|
|
9111
|
+
}
|
|
9112
|
+
}
|
|
9113
|
+
],
|
|
9114
|
+
"responses": {
|
|
9115
|
+
"200": {
|
|
9116
|
+
"description": "Category record",
|
|
9117
|
+
"content": {
|
|
9118
|
+
"application/json": {
|
|
9119
|
+
"schema": {
|
|
9120
|
+
"$ref": "#/components/schemas/SuccessResponse"
|
|
9121
|
+
}
|
|
9122
|
+
}
|
|
9123
|
+
}
|
|
9124
|
+
}
|
|
9125
|
+
},
|
|
9126
|
+
"description": "Fetch a single TOP-level member category by `profession_id`. Read-only.\n\nA Top Category is the highest level of the 3-tier member classification. Backed by BD's `list_professions` table.\n\n**Required:** `profession_id` (path parameter).\n\n**See also:** `listTopCategories` (enumerate), `listSubCategories` (sub-categories under this one; filter by `profession_id`).\n\n**Returns:** `{ status: \"success\", message: [{...record}] }` — array of 1 record with full fields.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
9127
|
+
}
|
|
9128
|
+
},
|
|
9129
|
+
"/api/v2/list_professions/create": {
|
|
9130
|
+
"post": {
|
|
9131
|
+
"operationId": "createTopCategory",
|
|
9132
|
+
"summary": "Create a category",
|
|
9133
|
+
"tags": [
|
|
9134
|
+
"Categories"
|
|
9135
|
+
],
|
|
9136
|
+
"requestBody": {
|
|
9137
|
+
"required": true,
|
|
9138
|
+
"content": {
|
|
9139
|
+
"application/x-www-form-urlencoded": {
|
|
9140
|
+
"schema": {
|
|
9141
|
+
"type": "object",
|
|
9142
|
+
"required": [
|
|
9143
|
+
"name",
|
|
9144
|
+
"filename"
|
|
9145
|
+
],
|
|
9146
|
+
"properties": {
|
|
9147
|
+
"name": {
|
|
9148
|
+
"type": "string",
|
|
9149
|
+
"description": "Top-level category name (e.g. \"Restaurants\", \"Dentists\")."
|
|
9150
|
+
},
|
|
9151
|
+
"filename": {
|
|
9152
|
+
"type": "string",
|
|
9153
|
+
"description": "URL-slug form of the name (e.g. \"restaurants\"). Used in public profile URL paths."
|
|
9154
|
+
},
|
|
9155
|
+
"desc": {
|
|
9156
|
+
"type": "string",
|
|
9157
|
+
"description": "Long description / summary for the category."
|
|
9158
|
+
},
|
|
9159
|
+
"keywords": {
|
|
9160
|
+
"type": "string",
|
|
9161
|
+
"description": "SEO keywords, comma-separated."
|
|
9162
|
+
},
|
|
9163
|
+
"icon": {
|
|
9164
|
+
"type": "string",
|
|
9165
|
+
"description": "Icon identifier (e.g. a Font Awesome class or image filename)."
|
|
9166
|
+
},
|
|
9167
|
+
"sort_order": {
|
|
9168
|
+
"type": "integer",
|
|
9169
|
+
"description": "Display order among top-level categories. Lower = earlier."
|
|
9170
|
+
},
|
|
9171
|
+
"lead_price": {
|
|
9172
|
+
"type": "number",
|
|
9173
|
+
"description": "Per-lead price charged for leads matching this category (decimal)."
|
|
9174
|
+
},
|
|
9175
|
+
"image": {
|
|
9176
|
+
"type": "string",
|
|
9177
|
+
"description": "Image filename for the category icon/banner."
|
|
9178
|
+
}
|
|
9179
|
+
}
|
|
9180
|
+
}
|
|
9181
|
+
}
|
|
9182
|
+
}
|
|
9183
|
+
},
|
|
9184
|
+
"responses": {
|
|
9185
|
+
"200": {
|
|
9186
|
+
"description": "Category created",
|
|
9187
|
+
"content": {
|
|
9188
|
+
"application/json": {
|
|
9189
|
+
"schema": {
|
|
9190
|
+
"$ref": "#/components/schemas/SuccessResponse"
|
|
9191
|
+
}
|
|
9192
|
+
}
|
|
9193
|
+
}
|
|
9194
|
+
}
|
|
9195
|
+
},
|
|
9196
|
+
"description": "Create a new TOP-level member category. Writes live data.\n\nA Top Category is the highest level of the 3-tier member classification (e.g., \"Restaurants\"). It populates the `profession_id` field on user records. Backed by BD's `list_professions` table.\n\n**Required:** `name`, `filename`.\n\n**Parameter guidance:**\n- `name` — human-readable (e.g. \"Restaurants\", \"Dentists\")\n- `filename` — URL-slug form (e.g. \"restaurants\") used in public member profile URLs\n- `desc`, `keywords`, `icon`, `sort_order`, `lead_price`, `image` — all optional\n\n**See also:** `listTopCategories` (list all), `getTopCategory` (by ID), `createSubCategory` (add a sub-category under this top).\n\n**Writes live data:** changes are immediately visible on the public site.\n\n**Returns:** `{ status: \"success\", message: {...createdRecord} }` including the new `profession_id`. Use that value to populate `users_data.profession_id` on member records.\n\n**Common workflow — full 3-tier setup (\"create Restaurants → Sushi → assign Alice\"):**\n\n1. `createTopCategory` with `name=\"Restaurants\"`, `filename=\"restaurants\"` → returns `profession_id` (e.g. 42)\n2. `createSubCategory` with `name=\"Sushi\"`, `profession_id=42`, `filename=\"sushi\"` → returns `service_id` (e.g. 17)\n3. Assign Alice: `updateUser` with `user_id=<Alice>`, `profession_id=42`, `services=\"17\"` (simple), OR `createMemberSubCategoryLink` with `user_id=<Alice>`, `service_id=17`, `avg_price=...`, `specialty=1` (with per-link metadata)\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
9197
|
+
}
|
|
9198
|
+
},
|
|
9199
|
+
"/api/v2/list_professions/update": {
|
|
9200
|
+
"put": {
|
|
9201
|
+
"operationId": "updateTopCategory",
|
|
9202
|
+
"summary": "Update a category",
|
|
9203
|
+
"tags": [
|
|
9204
|
+
"Categories"
|
|
9205
|
+
],
|
|
9206
|
+
"requestBody": {
|
|
9207
|
+
"required": true,
|
|
9208
|
+
"content": {
|
|
9209
|
+
"application/x-www-form-urlencoded": {
|
|
9210
|
+
"schema": {
|
|
9211
|
+
"type": "object",
|
|
9212
|
+
"required": [
|
|
9213
|
+
"profession_id"
|
|
9214
|
+
],
|
|
9215
|
+
"properties": {
|
|
9216
|
+
"profession_id": {
|
|
9217
|
+
"type": "integer",
|
|
9218
|
+
"description": "The top-level category ID to update (from createTopCategory / listTopCategories)."
|
|
9219
|
+
},
|
|
9220
|
+
"name": {
|
|
9221
|
+
"type": "string"
|
|
9222
|
+
},
|
|
9223
|
+
"filename": {
|
|
9224
|
+
"type": "string"
|
|
9225
|
+
},
|
|
9226
|
+
"desc": {
|
|
9227
|
+
"type": "string"
|
|
9228
|
+
},
|
|
9229
|
+
"keywords": {
|
|
9230
|
+
"type": "string"
|
|
9231
|
+
},
|
|
9232
|
+
"icon": {
|
|
9233
|
+
"type": "string"
|
|
9234
|
+
},
|
|
9235
|
+
"sort_order": {
|
|
9236
|
+
"type": "integer"
|
|
9237
|
+
},
|
|
9238
|
+
"lead_price": {
|
|
9239
|
+
"type": "number"
|
|
9240
|
+
},
|
|
9241
|
+
"image": {
|
|
9242
|
+
"type": "string"
|
|
9243
|
+
}
|
|
9244
|
+
}
|
|
9245
|
+
}
|
|
9246
|
+
}
|
|
9247
|
+
}
|
|
9248
|
+
},
|
|
9249
|
+
"responses": {
|
|
9250
|
+
"200": {
|
|
9251
|
+
"description": "Category updated",
|
|
9252
|
+
"content": {
|
|
9253
|
+
"application/json": {
|
|
9254
|
+
"schema": {
|
|
9255
|
+
"$ref": "#/components/schemas/SuccessResponse"
|
|
9256
|
+
}
|
|
9257
|
+
}
|
|
9258
|
+
}
|
|
9259
|
+
}
|
|
9260
|
+
},
|
|
9261
|
+
"description": "Update an existing TOP-level member category by `profession_id`. Fields omitted are untouched. Writes live data.\n\n**Required:** `profession_id`.\n\n**See also:** `createTopCategory` (add new), `deleteTopCategory` (remove).\n\n**Writes live data:** changes are immediately visible on the public site.\n\n**Returns:** `{ status: \"success\", message: {...updatedRecord} }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
9262
|
+
}
|
|
9263
|
+
},
|
|
9264
|
+
"/api/v2/list_professions/delete": {
|
|
9265
|
+
"delete": {
|
|
9266
|
+
"operationId": "deleteTopCategory",
|
|
9267
|
+
"summary": "Delete a category",
|
|
9268
|
+
"tags": [
|
|
9269
|
+
"Categories"
|
|
9270
|
+
],
|
|
9271
|
+
"requestBody": {
|
|
9272
|
+
"required": true,
|
|
9273
|
+
"content": {
|
|
9274
|
+
"application/x-www-form-urlencoded": {
|
|
9275
|
+
"schema": {
|
|
9276
|
+
"type": "object",
|
|
9277
|
+
"required": [
|
|
9278
|
+
"profession_id"
|
|
9279
|
+
],
|
|
9280
|
+
"properties": {
|
|
9281
|
+
"profession_id": {
|
|
9282
|
+
"type": "integer",
|
|
9283
|
+
"description": "The top-level category ID to delete."
|
|
9284
|
+
}
|
|
9285
|
+
}
|
|
9286
|
+
}
|
|
9287
|
+
}
|
|
9288
|
+
}
|
|
9289
|
+
},
|
|
9290
|
+
"responses": {
|
|
9291
|
+
"200": {
|
|
9292
|
+
"description": "Category deleted",
|
|
9293
|
+
"content": {
|
|
9294
|
+
"application/json": {
|
|
9295
|
+
"schema": {
|
|
9296
|
+
"$ref": "#/components/schemas/DeleteResponse"
|
|
9297
|
+
}
|
|
9298
|
+
}
|
|
9299
|
+
}
|
|
9300
|
+
}
|
|
9301
|
+
},
|
|
9302
|
+
"description": "Permanently delete a TOP-level member category by `profession_id`. Destructive — cannot be undone via API.\n\n**Required:** `profession_id`.\n\n**Destructive:** confirm intent with the user. Members who referenced this `profession_id` will have orphan references. Sub Categories under this top (with matching `profession_id` in `list_services`) also become orphaned — consider reassigning or deleting them first.\n\n**See also:** `updateTopCategory` (modify without removing).\n\n**Returns:** `{ status: \"success\", message: \"list_professions record was deleted\" }`.\n\n\n---\n\n**Member Category Hierarchy (3 levels):**\n\nBD classifies members through a 3-level taxonomy — AI agents MUST understand all three to correctly create, assign, and query member categories:\n\n| Level | Tool nicknames | Endpoint | BD internal table | Key field | Parent reference |\n|---|---|---|---|---|---|\n| **1. Top Category** | `listTopCategories`, `createTopCategory`, etc. | `/api/v2/list_professions/*` | `list_professions` | `profession_id` (PK) | — |\n| **2. Sub Category** | `listSubCategories`, `createSubCategory`, etc. | `/api/v2/list_services/*` | `list_services` | `service_id` (PK) | `profession_id` → parent Top Category; `master_id` → parent Sub Category (for sub-sub nesting; 0 = direct child of Top) |\n| **3. Member ↔ Sub Category link** | `listMemberSubCategoryLinks`, `createMemberSubCategoryLink`, etc. | `/api/v2/rel_services/*` | `rel_services` | `rel_id` (PK) | `user_id` → member; `service_id` → Sub Category |\n\n**How a member gets classified on their public profile:**\n- `users_data.profession_id` → points at a single Top Category (the member's primary classification; shown in URL slug)\n- `users_data.services` → CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)\n- `rel_services` rows (Member ↔ Sub Category links) → used when you need per-link metadata like `avg_price`, `specialty`, `num_completed`. Optional; most sites use just the CSV field.\n\n**Sub-sub-categories:** `createSubCategory` with `master_id=<parent service_id>` creates a Sub Category nested under another Sub Category (a \"sub-sub\"). `master_id=0` (default) means the Sub Category sits directly under a Top Category (the `profession_id`).\n\n**There is NO `createProfession` or `createService` tool in this MCP** — those are the BD internal resource names. Use the tools named above.\n\n\n_Auth: `X-Api-Key` header. Rate limit: 100 req/60s (on 429, back off 60s). Errors: `{ \"status\": \"error\", \"message\": \"...\" }` with standard HTTP codes._"
|
|
9303
|
+
}
|
|
9278
9304
|
}
|
|
9279
9305
|
},
|
|
9280
9306
|
"tags": [
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "brilliant-directories-mcp",
|
|
3
3
|
"mcpName": "io.github.brilliantdirectories/brilliant-directories-mcp",
|
|
4
|
-
"version": "
|
|
4
|
+
"version": "3.0.0",
|
|
5
5
|
"description": "Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.",
|
|
6
6
|
"main": "index.js",
|
|
7
7
|
"bin": {
|