deleteTopCategory
Permanently delete a top-level member category by profession ID. Members and subcategories become orphaned; reassign them first to prevent data loss.
Instructions
Delete a category - Permanently delete a TOP-level member category by profession_id. Destructive - cannot be undone via API.
Use when: removing an unused top-level category. Any members with matching profession_id become orphaned - reassign them first. Any Sub Categories (list_services rows) under this top also orphan - delete or re-parent them.
Required: profession_id.
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.
Bound-page caveat: if this category's filename has a seo_type=profile_search_results web page bound to it, deleting the category orphans that page (it'll render empty — no category to query). The wrapper rejects deletes that would orphan a bound page — delete or repurpose the bound page first.
See also: updateTopCategory (modify without removing).
Returns: { status: "success", message: "list_professions record was deleted" }.
How a member gets classified on their public profile:
users_data.profession_id-> points at a single Top Category (the member's primary classification; shown in URL slug)users_data.services-> CSV of Sub Category IDs the member is tagged with (multiple allowed; simpler than the join table)rel_servicesrows (Member ↔ Sub Category links) -> used when you need per-link metadata likeavg_price,specialty,num_completed. Optional; most sites use just the CSV field.
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).
There is NO createProfession or createService tool in this MCP — those are BD's internal table names. Use createTopCategory / createSubCategory instead (BD's table-name → tool-name mapping is documented in Rule: Table to endpoint).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| profession_id | Yes | The top-level category ID to delete. |