brilliant-directories-mcp 5.3.2 → 6.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.
Files changed (2) hide show
  1. package/openapi/bd-api.json +27 -68
  2. package/package.json +1 -1
@@ -4043,59 +4043,6 @@
4043
4043
  "description": "Fetch a single posttype record. Read-only.\n\n**Use when:** checking the configuration of one post type (which `data_type` family, whether active, custom field config). Commonly followed by `getPostTypeCustomFields` to enumerate per-type fields.\n\n**Required:** `data_id`.\n\n**See also:** `listPostTypes` (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._"
4044
4044
  }
4045
4045
  },
4046
- "/api/v2/data_categories/create": {
4047
- "post": {
4048
- "operationId": "createPostType",
4049
- "summary": "Create a post type",
4050
- "tags": [
4051
- "Post Types"
4052
- ],
4053
- "requestBody": {
4054
- "required": true,
4055
- "content": {
4056
- "application/x-www-form-urlencoded": {
4057
- "schema": {
4058
- "type": "object",
4059
- "required": [
4060
- "data_name"
4061
- ],
4062
- "properties": {
4063
- "data_name": {
4064
- "type": "string"
4065
- },
4066
- "data_active": {
4067
- "type": "integer",
4068
- "enum": [
4069
- 0,
4070
- 1
4071
- ]
4072
- },
4073
- "category_tab": {
4074
- "type": "string"
4075
- },
4076
- "profile_tab": {
4077
- "type": "string"
4078
- }
4079
- }
4080
- }
4081
- }
4082
- }
4083
- },
4084
- "responses": {
4085
- "200": {
4086
- "description": "Post type created",
4087
- "content": {
4088
- "application/json": {
4089
- "schema": {
4090
- "$ref": "#/components/schemas/SuccessResponse"
4091
- }
4092
- }
4093
- }
4094
- }
4095
- },
4096
- "description": "Create a new posttype record. Writes live data.\n\n**Use when:** adding a new content type to the site (e.g., \"Podcasts\"). Rare — most sites use BD's built-in post types. Requires admin-level changes to custom fields afterward.\n\n**Required:** `data_name`.\n\n**Enums:** `data_active`: `0`=Inactive, `1`=Active.\n\n**See also:** `updatePostType` (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._"
4097
- }
4098
- },
4099
4046
  "/api/v2/data_categories/custom_fields": {
4100
4047
  "post": {
4101
4048
  "operationId": "getPostTypeCustomFields",
@@ -4179,7 +4126,7 @@
4179
4126
  }
4180
4127
  }
4181
4128
  },
4182
- "description": "Update an existing posttype record by ID. Fields omitted are untouched. Writes live data.\n\n**Use when:** toggling a post type active/inactive, renaming, or changing per-page display counts. For custom-field changes you typically work in the BD admin UI.\n\n**Required:** `data_id`.\n\n**See also:** `createPostType` (add new), `deletePostType` (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._"
4129
+ "description": "Update an existing posttype record by ID. Fields omitted are untouched. Writes live data.\n\n**Use when:** toggling a post type active/inactive, renaming, or changing per-page display counts. For custom-field changes you typically work in the BD admin UI.\n\n**Required:** `data_id`.\n\n**See also:** `deletePostType` (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._"
4183
4130
  }
4184
4131
  },
4185
4132
  "/api/v2/data_categories/delete": {
@@ -4330,7 +4277,7 @@
4330
4277
  }
4331
4278
  }
4332
4279
  },
4333
- "description": "Create a new unsubscribe record. Writes live data.\n\n**Use when:** programmatically opting a member out of emails (e.g., from an external unsubscribe form or CRM sync). BD adds entries itself when members click email unsubscribe links.\n\n**Required:** `email`.\n\n**Enums:** `definitive`: `0`, `1`.\n\n**See also:** `updateUnsubscribe` (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._"
4280
+ "description": "Create a new unsubscribe record. Writes live data.\n\n**Use when:** programmatically opting a member out of emails (e.g., from an external unsubscribe form or CRM sync). BD adds entries itself when members click email unsubscribe links.\n\n**Required:** `email`.\n\n**Enums:** `definitive`: `0`, `1`.\n\n**See also:** `updateUnsubscribe` (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**`email` is the only meaningful input.** Pass the email address to opt out. BD adds unsubscribe records to its global unsubscribe list — this applies across all email campaigns for the site. There is no \"unsubscribe from some lists but not others\" granularity via this endpoint; it's all-or-nothing.\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._"
4334
4281
  }
4335
4282
  },
4336
4283
  "/api/v2/unsubscribe_list/update": {
@@ -4835,7 +4782,7 @@
4835
4782
  }
4836
4783
  }
4837
4784
  },
4838
- "description": "Create a new emailtemplate record. Writes live data.\n\n**Use when:** adding a new transactional/marketing template. Rare — most BD email templates are built into the admin UI.\n\n**Required:** `email_name`.\n\n**Enums:** `signature`: `0`, `1`; `notemplate`: `0`, `1`; `unsubscribe_link`: `0`, `1`.\n\n**Parameter interactions:**\n- `email_subject` and `email_body` can use template tokens (e.g. `%%%website_name%%%`, recipient field tokens)\n- `email_body` supports HTML\n\n**See also:** `updateEmailTemplate` (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._"
4785
+ "description": "Create a new emailtemplate record. Writes live data.\n\n**Use when:** adding a new transactional/marketing template. Rare — most BD email templates are built into the admin UI.\n\n**Required:** `email_name`.\n\n**Enums:** `signature`: `0`, `1`; `notemplate`: `0`, `1`; `unsubscribe_link`: `0`, `1`.\n\n**Parameter interactions:**\n- `email_subject` and `email_body` can use template tokens (e.g. `%%%website_name%%%`, recipient field tokens)\n- `email_body` supports HTML\n\n**See also:** `updateEmailTemplate` (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**On create: `email_name` is the only required field.** Subject and body are optional at create time — you can create a template stub and fill in `email_subject` / `email_body` via `updateEmailTemplate` later. This lets you programmatically scaffold templates before customizing them via the admin UI.\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._"
4839
4786
  }
4840
4787
  },
4841
4788
  "/api/v2/email_templates/update": {
@@ -5028,15 +4975,26 @@
5028
4975
  },
5029
4976
  "form_action": {
5030
4977
  "type": "string",
5031
- "default": "post"
4978
+ "default": "post",
4979
+ "enum": [
4980
+ "post",
4981
+ "get"
4982
+ ],
4983
+ "description": "**post** = form submits via POST body (default, most forms). **get** = form submits as URL query string (use for bookmarkable search/filter forms)."
5032
4984
  },
5033
4985
  "form_layout": {
5034
4986
  "type": "string",
5035
- "default": "bootstrap"
4987
+ "default": "bootstrapvertical",
4988
+ "enum": [
4989
+ "bootstrapvertical",
4990
+ "bootstrap"
4991
+ ],
4992
+ "description": "**bootstrapvertical** = Labels Above Inputs (default). **bootstrap** = Labels Left of Inputs."
5036
4993
  },
5037
4994
  "form_table": {
5038
4995
  "type": "string",
5039
- "description": "Target DB table"
4996
+ "description": "Database table the form submissions post into. Default: `website_contacts`. Override only when building a form that posts into a different BD table.",
4997
+ "default": "website_contacts"
5040
4998
  },
5041
4999
  "form_class": {
5042
5000
  "type": "string"
@@ -5068,7 +5026,7 @@
5068
5026
  }
5069
5027
  }
5070
5028
  },
5071
- "description": "Create a new form record. Writes live data.\n\n**Use when:** adding a new form container. Add fields afterward with `createFormField`.\n\n**Required:** `form_name`, `form_title`, `form_action`, `form_layout`, `form_table`.\n\n**Enums:** `form_email_on`: `0`, `1`.\n\n**Parameter interactions:**\n- After creating the form, add fields via `createFormField` using the returned form identifier\n\n**See also:** `updateForm` (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._"
5029
+ "description": "Create a new form record. Writes live data.\n\n**Use when:** adding a new form container. Add fields afterward with `createFormField`.\n\n**Required:** `form_name`, `form_title`, `form_action`, `form_layout`, `form_table`.\n\n**Enums:** `form_email_on`: `0`, `1`.\n\n**Parameter interactions:**\n- After creating the form, add fields via `createFormField` using the returned form identifier\n\n**See also:** `updateForm` (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**Field defaults and valid values (from BD admin form-builder UI, confirmed 2026-04-18):**\n- `form_action` — `post` (default, form submits via POST) or `get` (form submits via URL query string). Most forms use `post`; use `get` only for search/filter forms where the submission should be bookmarkable.\n- `form_layout` — `bootstrapvertical` (default; Labels Above Inputs) or `bootstrap` (Labels Left of Inputs).\n- `form_table` — the database table submissions are posted into. Default: `website_contacts`. Override only when building a form that posts into a different BD table (rare; usually a custom workflow).\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._"
5072
5030
  }
5073
5031
  },
5074
5032
  "/api/v2/form/update": {
@@ -5246,11 +5204,11 @@
5246
5204
  },
5247
5205
  "field_name": {
5248
5206
  "type": "string",
5249
- "description": "DB column name"
5207
+ "description": "Internal system key for this field. **Underscores only, no spaces** — e.g. `first_name`, `company_email`. Used as the HTML `name` attribute."
5250
5208
  },
5251
5209
  "field_text": {
5252
5210
  "type": "string",
5253
- "description": "Display label"
5211
+ "description": "Public-facing display label shown to the user. Free-form text — e.g. \"First Name\", \"Your Email Address\"."
5254
5212
  },
5255
5213
  "field_type": {
5256
5214
  "type": "string",
@@ -5287,7 +5245,7 @@
5287
5245
  "Category",
5288
5246
  "Years"
5289
5247
  ],
5290
- "description": "Form field type. Authoritative list from BD admin form-field editor, grouped by category:\\n\\nSELECT FIELDS (user picks from options):\\n Checkbox = Checkboxes (multi-select)\\n Select = Dropdown list (single-select)\\n Radio = Multiple choice radios (single-select)\\n YesNo = Yes or No toggle\\n\\nTEXT INPUTS:\\n Custom = Custom HTML injection\\n Email = Email address input (validates format)\\n HTML = Section title / HTML heading (display-only)\\n Button = Submit form button\\n Textbox = Single-line text input\\n textarea = Multi-line textarea (note: lowercase)\\n Url = Website URL input\\n\\nFANCY FIELDS:\\n Date = Calendar date picker\\n DateTimeLocal = Calendar date+time picker\\n File = File upload\\n FroalaEditor = Froala rich text editor (basic)\\n FroalaEditorUserUpload = Froala + user image upload\\n FroalaEditorUserUploadPreMadeElem = Froala + upload + pre-made elements\\n FroalaEditorAdmin = Froala with admin media manager access\\n Tip = Help alert box (display-only)\\n Hidden = Hidden field (not rendered, stores value)\\n Country = Country dropdown\\n State = State dropdown\\n Number = Integer-only number input\\n Password = Password field (masked)\\n Phone = Phone number input\\n CountryCodePhone = Phone input with country code\\n Pricebox = Price input\\n ReCaptcha = Google reCAPTCHA security\\n HoneyPot = Hidden honeypot (anti-spam)\\n Category = Top-level category list\\n Years = Year picker\\n\\nNote on casing: most values are TitleCase but \"textarea\" is lowercase — copy exact spelling from the enum. For most simple text collection use Textbox; for paragraphs use textarea; for emails use Email so BD validates the format.\\n\\nFor Checkbox / Select / Radio types, you must also supply the options list via the field_options parameter (if exposed)."
5248
+ "description": "Form field type. See full list grouped by category (Select / Text inputs / Fancy fields) in the tool description."
5291
5249
  },
5292
5250
  "field_order": {
5293
5251
  "type": "integer"
@@ -5331,7 +5289,7 @@
5331
5289
  }
5332
5290
  }
5333
5291
  },
5334
- "description": "Create a new formfield record. Writes live data.\n\n**Use when:** adding an input to an existing form.\n\n**Required:** `form_name`, `field_name`, `field_text`, `field_type`, `field_order`.\n\n**Enums:** `field_required`: `0`, `1`.\n\n**Parameter interactions:**\n- `form_id` / `form_name` — the parent form (from `createForm` or `listForms`)\n- Field type and options depend on the form type; validate against the form's field schema\n\n**See also:** `updateFormField` (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._"
5292
+ "description": "Create a new formfield record. Writes live data.\n\n**Use when:** adding an input to an existing form.\n\n**Required:** `form_name`, `field_name`, `field_text`, `field_type`, `field_order`.\n\n**Enums:** `field_required`: `0`, `1`.\n\n**Parameter interactions:**\n- `form_id` / `form_name` — the parent form (from `createForm` or `listForms`)\n- Field type and options depend on the form type; validate against the form's field schema\n\n**See also:** `updateFormField` (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**`field_type` valid values (BD admin form-builder UI, full list):**\n\n*Select-type fields:* `Checkbox` (checkboxes), `Select` (dropdown list), `Radio` (radio buttons), `YesNo` (yes/no toggle)\n\n*Text inputs:* `Custom` (custom HTML), `Email`, `HTML` (section title / heading), `Button` (submit button), `Textbox` (single-line text), `textarea` (paragraph), `Url` (website URL)\n\n*Fancy fields:* `Date` (date picker), `DateTimeLocal` (date + time picker), `File` (file upload), `FroalaEditor` (rich text — basic), `FroalaEditorUserUpload` (+ image upload), `FroalaEditorUserUploadPreMadeElem` (+ pre-made elements), `FroalaEditorAdmin` (+ media manager), `Tip` (help alert box), `Hidden`, `Country` (country list), `State` (state list), `Number` (integer), `Password`, `Phone`, `CountryCodePhone`, `Pricebox`, `ReCaptcha` (Google reCAPTCHA), `HoneyPot` (spam protection), `Category` (top-level category list), `Years` (year picker)\n\n**Field naming rules:**\n- `field_name` — internal system key. **Underscores only, no spaces.** E.g. `first_name`, `company_email`. Used as HTML `name` attribute.\n- `field_text` — public-facing display label shown to form users. Free-form, e.g. \"First Name\", \"Your Email Address\".\n\n**Form composition rule:** a form should have **exactly ONE `Button` field** (the submit trigger). Adding multiple Button fields causes UI confusion.\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._"
5335
5293
  }
5336
5294
  },
5337
5295
  "/api/v2/form_fields/update": {
@@ -7702,7 +7660,7 @@
7702
7660
  }
7703
7661
  }
7704
7662
  },
7705
- "description": "Create a new tagrelationship record. Writes live data.\n\n**Use when:** attaching an existing tag to a record (member, post, etc.). The alternative for members is setting the `member_tags` field via `updateUser` with `member_tag_action=1`.\n\n**Required:** `tag_id`, `object_id`, `tag_type_id`, `added_by`.\n\n**Parameter interactions:**\n- Attaches an existing tag to an existing record. Both sides must exist — use `listTags` and the target resource's list to discover IDs\n\n**See also:** `updateTagRelationship` (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._"
7663
+ "description": "Create a new tagrelationship record. Writes live data.\n\n**Use when:** attaching an existing tag to a record (member, post, etc.). The alternative for members is setting the `member_tags` field via `updateUser` with `member_tag_action=1`.\n\n**Required:** `tag_id`, `object_id`, `tag_type_id`, `added_by`.\n\n**Parameter interactions:**\n- Attaches an existing tag to an existing record. Both sides must exist — use `listTags` and the target resource's list to discover IDs\n\n**See also:** `updateTagRelationship` (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**`tag_type_id` + `object_id` — how to target the right record (from BD `tag_types` table):**\n\nThe `tag_type_id` determines WHICH resource/table the `object_id` lives in. Discover mapping via `listTagTypes` — each tag type row has a `table_relation` field naming its target table. Example mapping:\n\n| tag_type_id | type_name | Target table (table_relation) | What object_id references |\n|---|---|---|---|\n| 1 | Users | `users_data` | `user_id` |\n| (other rows) | (other types) | e.g. `data_widgets`, `menus`, `forms` | That table's primary key |\n\n**Process:** call `listTagTypes` first to see the `tag_type_id` → `table_relation` mapping on your site, then pick the appropriate `tag_type_id` and supply the matching record's PK as `object_id`. Widgets, menus, and forms all support tags via this same mechanism.\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._"
7706
7664
  }
7707
7665
  },
7708
7666
  "/api/v2/rel_tags/update": {
@@ -7912,7 +7870,7 @@
7912
7870
  }
7913
7871
  }
7914
7872
  },
7915
- "description": "Create a new smartlist record. Writes live data.\n\n**Use when:** programmatically saving a filter configuration for later reuse. `smart_list_type` determines the data source (`members`, `leads`, `reviews`, etc.).\n\n**Required:** `smart_list_name`, `smart_list_type`, `smart_list_created_by`.\n\n**Parameter interactions:**\n- `smart_list_type` — data source (see Enums)\n- `smart_list_created_by` — admin user ID creating the list\n- `smart_list_query_params` — JSON/string of filter criteria specific to the chosen type\n- `schedule` — recurrence if the list should auto-refresh\n\n**See also:** `updateSmartList` (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._"
7873
+ "description": "Create a new smartlist record. Writes live data.\n\n**Use when:** programmatically saving a filter configuration for later reuse. `smart_list_type` determines the data source (`members`, `leads`, `reviews`, etc.).\n\n**Required:** `smart_list_name`, `smart_list_type`, `smart_list_created_by`.\n\n**Parameter interactions:**\n- `smart_list_type` — data source (see Enums)\n- `smart_list_created_by` — admin user ID creating the list\n- `smart_list_query_params` — JSON/string of filter criteria specific to the chosen type\n- `schedule` — recurrence if the list should auto-refresh\n\n**See also:** `updateSmartList` (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**`smart_list_query_params` format depends on `smart_list_type`:**\n\n- For `smart_list_type=newsletter`: store a URL string (admin view uses it directly as an href link — no filter semantics).\n- For ALL other types (`members`, `leads`, `reviews`, `transaction`, `forms_inbox`): pass a **JSON string of filter key-value pairs**, e.g. `{\"subscription_id\":\"1\",\"active\":\"1\"}`. The backend encrypts it internally before storing.\n- If empty / no filters: pass `\"NA\"` (the controller defaults missing values to this).\n\nThe API accepts the value as a plain string; BD handles the internal encryption. Don't pre-encrypt client-side — you'll get double-encrypted garbage. Use the JSON-key-value format for filterable types.\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._"
7916
7874
  }
7917
7875
  },
7918
7876
  "/api/v2/smart_lists/update": {
@@ -8703,7 +8661,7 @@
8703
8661
  "post": {
8704
8662
  "operationId": "createRedirect",
8705
8663
  "summary": "Create a redirect",
8706
- "description": "Create a new 301 redirect rule. type, old_filename, and new_filename are required.\n\n**Use when:** preserving SEO after any URL change — slug rename on a member profile, post, page, or category. BD auto-creates some redirects on its own (admin-triggered renames), but you must create them manually for API-triggered changes. Avoid duplicate `old_filename` values.\n\n**Required:** `type`, `old_filename`, `new_filename`.\n\n**Parameter interactions:**\n- `type` — source category: `profile`, `post`, `category`, `custom`, etc.\n- `old_filename` / `new_filename` — URL paths relative to the domain root (not full URLs)\n- `db_id` — database record ID of the source content if the redirect ties to one; otherwise 0\n\n**See also:** `updateRedirect` (modify existing).\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._",
8664
+ "description": "Create a new 301 redirect rule. type, old_filename, and new_filename are required.\n\n**Use when:** preserving SEO after any URL change — slug rename on a member profile, post, page, or category. BD auto-creates some redirects on its own (admin-triggered renames), but you must create them manually for API-triggered changes. Avoid duplicate `old_filename` values.\n\n**Required:** `type`, `old_filename`, `new_filename`.\n\n**Parameter interactions:**\n- `type` — source category: `profile`, `post`, `category`, `custom`, etc.\n- `old_filename` / `new_filename` — URL paths relative to the domain root (not full URLs)\n- `db_id` — database record ID of the source content if the redirect ties to one; otherwise 0\n\n**See also:** `updateRedirect` (modify existing).\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**`type` default: `custom`** — use `custom` unless you're explicitly mirroring BD's auto-generated redirect types (`profile`, `post`, `category`). Most API-created redirects should use `custom` since they're not tied to an auto-rename event from the BD admin UI.\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._",
8707
8665
  "tags": [
8708
8666
  "Redirects"
8709
8667
  ],
@@ -8721,7 +8679,8 @@
8721
8679
  "properties": {
8722
8680
  "type": {
8723
8681
  "type": "string",
8724
- "description": "Category of the redirect source (profile, post, category, custom, etc.)"
8682
+ "description": "Redirect type category. Default: `custom` for API-created redirects. Other values (`profile`, `post`, `category`) are typically set by BD's auto-redirect logic on admin-triggered renames.",
8683
+ "default": "custom"
8725
8684
  },
8726
8685
  "old_filename": {
8727
8686
  "type": "string",
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": "5.3.2",
4
+ "version": "6.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": {