getMemberSubCategoryLink
Fetch a single member-subcategory link by its relation ID to get full details like pricing and specialty.
Instructions
Get a single user-service relationship - Fetch a single Member ↔ Sub Category link by rel_id. Read-only.
Use when: you have a rel_id and need the full link row. Rare - most workflows query by user_id or service_id via listMemberSubCategoryLinks.
Required: rel_id.
See also: listMemberSubCategoryLinks (enumerate, filter by user_id or service_id).
Returns: { status: "success", message: [{...record}] }.
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 |