getTopCategory
Fetch a top-level member category record by its profession_id. Returns name and filename by default; include full metadata with category schema.
Instructions
Get a single category - Fetch a single TOP-level member category by profession_id. Read-only.
Lean by default: keeps profession_id, name, filename. Strips SEO metadata. Pass include_category_schema=1 to restore.
A Top Category is the highest level of the 3-tier member classification. Backed by BD's list_professions table.
Use when: you already have a profession_id and need its full record (name, filename, etc.). For enumeration use listTopCategories.
Required: profession_id (path parameter).
See also: listTopCategories (enumerate), listSubCategories (sub-categories under this one; filter by profession_id).
Returns: { status: "success", message: [{...record}] } - array of 1 record with full fields.
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 | ||
| include_category_schema | No | Opt in to restore full category metadata: `desc` (SEO description), `keywords`, `image`, `icon`, `sort_order`, `lead_price`, `revision_timestamp`. Default lean keeps: category ID + `name` + `filename` + hierarchy links (`profession_id` on top/sub, `master_id` on sub for sub-sub parent). Hierarchy is always visible so agents can traverse top -> sub -> sub-sub without opt-in. |