deleteMemberSubCategoryLink
Permanently remove a member's link to a sub category using the link's unique rel_id. Destructive action that cannot be undone via API.
Instructions
Remove a service from a user - Permanently delete a Member ↔ Sub Category link by rel_id. Destructive - cannot be undone via API.
Removes 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.
Use when: removing a specific link row. Does NOT update the users_data.services CSV - that's a separate field; update it via updateUser if the service_id is also listed there.
Required: rel_id.
Returns: { status: "success", message: "rel_services 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 |
|---|---|---|---|
| rel_id | Yes |