@smartytalent/mcp-tools 0.9.35 → 0.9.36
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.
- package/dist/tools.json +39 -20
- package/package.json +1 -1
package/dist/tools.json
CHANGED
|
@@ -166,20 +166,24 @@
|
|
|
166
166
|
"type": "object",
|
|
167
167
|
"properties": {
|
|
168
168
|
"ad": {
|
|
169
|
-
"type": "object"
|
|
169
|
+
"type": "object",
|
|
170
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. Ads and their images are built for every recruitment process; `enabled` never gated anything, `generateImages` is always on (the env kill switch AD_IMAGE_GENERATION remains), `platforms` were never read (the platform lists are fixed in code). Removed in a later, breaking release together with settings.feedback; declared until then because the generated model whitelists keys."
|
|
170
171
|
},
|
|
171
172
|
"brand": {
|
|
172
173
|
"type": "object",
|
|
173
174
|
"description": "Brand rules the ad and careers generators read. Split by who can\nact on what: exact colours are applied by CODE (an image model\nonly ever approximates a hex), while the look-and-feel strings\nare fed to the image prompt. Keys: primaryColor / secondaryColor\n(^#[0-9a-fA-F]{6}$), photography, avoid, tone. Freeform for now;\na dedicated brand service is the endgame once logo variants,\ntypefaces and versioning arrive."
|
|
174
175
|
},
|
|
175
176
|
"conversation": {
|
|
176
|
-
"type": "object"
|
|
177
|
+
"type": "object",
|
|
178
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. The AI interview is part of the recruitment process (settings.automation on the job); `jobInterview.enabled` never had a reader. Removed in a later, breaking release; declared until then because the generated model whitelists keys."
|
|
177
179
|
},
|
|
178
180
|
"report": {
|
|
179
|
-
"type": "object"
|
|
181
|
+
"type": "object",
|
|
182
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. Reports run for EVERY active tenant (daily, weekly, monthly) and are downloaded in the report app (showReport meta.pdf); e-mail delivery is gone (a per-user preference is a later phase), so `emails` and `period` gate nothing. Removed in a later, breaking release; declared until then because the generated model whitelists keys."
|
|
180
183
|
},
|
|
181
184
|
"email": {
|
|
182
|
-
"type": "object"
|
|
185
|
+
"type": "object",
|
|
186
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. `domains` (trusted e-mail domains) never had a reader - inbound trust comes from the user registry and SPF/DKIM alignment. Removed in a later, breaking release; declared until then because the generated model whitelists keys."
|
|
183
187
|
},
|
|
184
188
|
"operation": {
|
|
185
189
|
"type": "object",
|
|
@@ -188,7 +192,7 @@
|
|
|
188
192
|
"feedback": {
|
|
189
193
|
"title": "TenantAttributesSettingsFeedbackSchema",
|
|
190
194
|
"type": "object",
|
|
191
|
-
"description": "Organisation-wide switch for outbound candidate feedback
|
|
195
|
+
"description": "DEPRECATED (2026-09-24, S.K.: settings.automation.feedback is the ONE control of feedback; this field will be removed in a later, breaking release). Organisation-wide legacy switch for outbound candidate feedback: absent = enabled; enabled=false makes feedback:resolve return enabled=false with reason disabled:tenant ONLY while settings.automation.feedback is absent on both the job and the tenant - once the new key is set at either level this field is ignored; default and per-job feedback rows stay stored. Explicitly validated: enabled must be a JSON boolean (a string is a 400). NOTE: the generated model whitelists keys, so this property MUST stay declared until the removal release.",
|
|
192
196
|
"properties": {
|
|
193
197
|
"enabled": {
|
|
194
198
|
"type": "boolean"
|
|
@@ -738,20 +742,24 @@
|
|
|
738
742
|
"type": "object",
|
|
739
743
|
"properties": {
|
|
740
744
|
"ad": {
|
|
741
|
-
"type": "object"
|
|
745
|
+
"type": "object",
|
|
746
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. Ads and their images are built for every recruitment process; `enabled` never gated anything, `generateImages` is always on (the env kill switch AD_IMAGE_GENERATION remains), `platforms` were never read (the platform lists are fixed in code). Removed in a later, breaking release together with settings.feedback; declared until then because the generated model whitelists keys."
|
|
742
747
|
},
|
|
743
748
|
"brand": {
|
|
744
749
|
"type": "object",
|
|
745
750
|
"description": "Brand rules the ad and careers generators read. Split by who can\nact on what: exact colours are applied by CODE (an image model\nonly ever approximates a hex), while the look-and-feel strings\nare fed to the image prompt. Keys: primaryColor / secondaryColor\n(^#[0-9a-fA-F]{6}$), photography, avoid, tone. Freeform for now;\na dedicated brand service is the endgame once logo variants,\ntypefaces and versioning arrive."
|
|
746
751
|
},
|
|
747
752
|
"conversation": {
|
|
748
|
-
"type": "object"
|
|
753
|
+
"type": "object",
|
|
754
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. The AI interview is part of the recruitment process (settings.automation on the job); `jobInterview.enabled` never had a reader. Removed in a later, breaking release; declared until then because the generated model whitelists keys."
|
|
749
755
|
},
|
|
750
756
|
"report": {
|
|
751
|
-
"type": "object"
|
|
757
|
+
"type": "object",
|
|
758
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. Reports run for EVERY active tenant (daily, weekly, monthly) and are downloaded in the report app (showReport meta.pdf); e-mail delivery is gone (a per-user preference is a later phase), so `emails` and `period` gate nothing. Removed in a later, breaking release; declared until then because the generated model whitelists keys."
|
|
752
759
|
},
|
|
753
760
|
"email": {
|
|
754
|
-
"type": "object"
|
|
761
|
+
"type": "object",
|
|
762
|
+
"description": "DEPRECATED (2026-09-24, S.K., PLAN_TENANT_SETTINGS_CLEANUP): ignored by the backend and stripped on write. `domains` (trusted e-mail domains) never had a reader - inbound trust comes from the user registry and SPF/DKIM alignment. Removed in a later, breaking release; declared until then because the generated model whitelists keys."
|
|
755
763
|
},
|
|
756
764
|
"operation": {
|
|
757
765
|
"type": "object",
|
|
@@ -760,7 +768,7 @@
|
|
|
760
768
|
"feedback": {
|
|
761
769
|
"title": "TenantAttributesSettingsFeedbackSchema",
|
|
762
770
|
"type": "object",
|
|
763
|
-
"description": "Organisation-wide switch for outbound candidate feedback
|
|
771
|
+
"description": "DEPRECATED (2026-09-24, S.K.: settings.automation.feedback is the ONE control of feedback; this field will be removed in a later, breaking release). Organisation-wide legacy switch for outbound candidate feedback: absent = enabled; enabled=false makes feedback:resolve return enabled=false with reason disabled:tenant ONLY while settings.automation.feedback is absent on both the job and the tenant - once the new key is set at either level this field is ignored; default and per-job feedback rows stay stored. Explicitly validated: enabled must be a JSON boolean (a string is a 400). NOTE: the generated model whitelists keys, so this property MUST stay declared until the removal release.",
|
|
764
772
|
"properties": {
|
|
765
773
|
"enabled": {
|
|
766
774
|
"type": "boolean"
|
|
@@ -5397,7 +5405,7 @@
|
|
|
5397
5405
|
"feedback": {
|
|
5398
5406
|
"title": "JobAttributesSettingsFeedbackSchema",
|
|
5399
5407
|
"type": "object",
|
|
5400
|
-
"description": "Per-job switch for outbound candidate feedback
|
|
5408
|
+
"description": "DEPRECATED (2026-09-24, S.K.: settings.automation.feedback is the ONE control of feedback; this field will be removed in a later, breaking release). Per-job legacy switch for outbound candidate feedback: absent = enabled; enabled=false makes feedback:resolve return enabled=false with reason disabled:job ONLY while settings.automation.feedback is absent on both the job and the tenant - once the new key is set at either level this field is ignored. Between the two legacy switches the tenant's wins. Explicitly validated: enabled must be a JSON boolean.",
|
|
5401
5409
|
"properties": {
|
|
5402
5410
|
"enabled": {
|
|
5403
5411
|
"type": "boolean"
|
|
@@ -5407,7 +5415,7 @@
|
|
|
5407
5415
|
"automation": {
|
|
5408
5416
|
"title": "JobAttributesSettingsAutomationSchema",
|
|
5409
5417
|
"type": "object",
|
|
5410
|
-
"description": "Per-job automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24): who runs each stage of THIS recruitment process. Values per key: auto = Boe runs the stage, manual = a human runs it (Boe leaves a task on the RecOps board and waits), off = the stage is not part of this process (the candidate moves on). Every key is optional: absent = the organisation's default (tenant.settings.automation), else the platform default (sourcing manual, everything else auto); the job overrides the tenant in BOTH directions. Read by the automation:resolve action at the head of the candidate-facing workflows and by feedback:resolve (feedback). PATCH merges this block PER KEY (send one switch at a time; a key sent as null clears the override). Writable only by sysowner / owner / admin / recops - any other role gets 403 on a payload that carries it, on POST and PATCH. Validated in code: interview and offer accept auto|manual, surveys accepts auto|off, the rest auto|manual|off; an unknown key or value is a 400 naming it.
|
|
5418
|
+
"description": "Per-job automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24): who runs each stage of THIS recruitment process. Values per key: auto = Boe runs the stage, manual = a human runs it (Boe leaves a task on the RecOps board and waits), off = the stage is not part of this process (the candidate moves on). Every key is optional: absent = the organisation's default (tenant.settings.automation), else the platform default (sourcing manual, everything else auto); the job overrides the tenant in BOTH directions. Read by the automation:resolve action at the head of the candidate-facing workflows and by feedback:resolve (feedback). PATCH merges this block PER KEY (send one switch at a time; a key sent as null clears the override). Writable only by sysowner / owner / admin / recops - any other role gets 403 on a payload that carries it, on POST and PATCH. Validated in code: interview and offer accept auto|manual, surveys accepts auto|off, the rest auto|manual|off; an unknown key or value is a 400 naming it. `feedback` here is the ONE control of feedback e-mails (S.K. 2026-09-24): the deprecated settings.feedback.enabled counts only while this key is absent on both the job and the tenant. The job build (Create Job From Brief) never generates this block: it keeps the row's values and seeds `off` for the stages the manager declared out of the process in the intake (brief.intakeContext.process).",
|
|
5411
5419
|
"properties": {
|
|
5412
5420
|
"sourcing": {
|
|
5413
5421
|
"type": "string",
|
|
@@ -6297,7 +6305,7 @@
|
|
|
6297
6305
|
"feedback": {
|
|
6298
6306
|
"title": "JobAttributesSettingsFeedbackSchema",
|
|
6299
6307
|
"type": "object",
|
|
6300
|
-
"description": "Per-job switch for outbound candidate feedback
|
|
6308
|
+
"description": "DEPRECATED (2026-09-24, S.K.: settings.automation.feedback is the ONE control of feedback; this field will be removed in a later, breaking release). Per-job legacy switch for outbound candidate feedback: absent = enabled; enabled=false makes feedback:resolve return enabled=false with reason disabled:job ONLY while settings.automation.feedback is absent on both the job and the tenant - once the new key is set at either level this field is ignored. Between the two legacy switches the tenant's wins. Explicitly validated: enabled must be a JSON boolean.",
|
|
6301
6309
|
"properties": {
|
|
6302
6310
|
"enabled": {
|
|
6303
6311
|
"type": "boolean"
|
|
@@ -6307,7 +6315,7 @@
|
|
|
6307
6315
|
"automation": {
|
|
6308
6316
|
"title": "JobAttributesSettingsAutomationSchema",
|
|
6309
6317
|
"type": "object",
|
|
6310
|
-
"description": "Per-job automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24): who runs each stage of THIS recruitment process. Values per key: auto = Boe runs the stage, manual = a human runs it (Boe leaves a task on the RecOps board and waits), off = the stage is not part of this process (the candidate moves on). Every key is optional: absent = the organisation's default (tenant.settings.automation), else the platform default (sourcing manual, everything else auto); the job overrides the tenant in BOTH directions. Read by the automation:resolve action at the head of the candidate-facing workflows and by feedback:resolve (feedback). PATCH merges this block PER KEY (send one switch at a time; a key sent as null clears the override). Writable only by sysowner / owner / admin / recops - any other role gets 403 on a payload that carries it, on POST and PATCH. Validated in code: interview and offer accept auto|manual, surveys accepts auto|off, the rest auto|manual|off; an unknown key or value is a 400 naming it.
|
|
6318
|
+
"description": "Per-job automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24): who runs each stage of THIS recruitment process. Values per key: auto = Boe runs the stage, manual = a human runs it (Boe leaves a task on the RecOps board and waits), off = the stage is not part of this process (the candidate moves on). Every key is optional: absent = the organisation's default (tenant.settings.automation), else the platform default (sourcing manual, everything else auto); the job overrides the tenant in BOTH directions. Read by the automation:resolve action at the head of the candidate-facing workflows and by feedback:resolve (feedback). PATCH merges this block PER KEY (send one switch at a time; a key sent as null clears the override). Writable only by sysowner / owner / admin / recops - any other role gets 403 on a payload that carries it, on POST and PATCH. Validated in code: interview and offer accept auto|manual, surveys accepts auto|off, the rest auto|manual|off; an unknown key or value is a 400 naming it. `feedback` here is the ONE control of feedback e-mails (S.K. 2026-09-24): the deprecated settings.feedback.enabled counts only while this key is absent on both the job and the tenant. The job build (Create Job From Brief) never generates this block: it keeps the row's values and seeds `off` for the stages the manager declared out of the process in the intake (brief.intakeContext.process).",
|
|
6311
6319
|
"properties": {
|
|
6312
6320
|
"sourcing": {
|
|
6313
6321
|
"type": "string",
|
|
@@ -22466,12 +22474,23 @@
|
|
|
22466
22474
|
"properties": {
|
|
22467
22475
|
"filterStatus": {
|
|
22468
22476
|
"type": "string",
|
|
22469
|
-
"description": "Returns reports with the
|
|
22477
|
+
"description": "Returns reports with the given status. Pass it explicitly - the backend applies NO default, so without it pending and failed rows come back too. The report app's history query is `filterStatus=active&sort=-created` (newest first; the status index carries the sort). One filter at a time: the backend serves a single index per request.",
|
|
22470
22478
|
"enum": [
|
|
22471
22479
|
"active",
|
|
22472
|
-
"
|
|
22480
|
+
"inactive",
|
|
22481
|
+
"pending",
|
|
22482
|
+
"archived",
|
|
22483
|
+
"failed"
|
|
22473
22484
|
]
|
|
22474
22485
|
},
|
|
22486
|
+
"filterResourceId": {
|
|
22487
|
+
"type": "string",
|
|
22488
|
+
"description": "Returns the reports of ONE resource (a job id, or the tenant id for the scheduled tenant reports). Served from the ResourceIndex in index order: `sort` is IGNORED next to it, and it cannot be combined with filterStatus or the created/modified window (one filter at a time). For the tenant history use `filterStatus=active&sort=-created` instead and read `resourceType` / `period` off the rows."
|
|
22489
|
+
},
|
|
22490
|
+
"sort": {
|
|
22491
|
+
"type": "string",
|
|
22492
|
+
"description": "`created` / `-created` / `modified` / `-modified`. Honoured alone and next to filterStatus; ignored next to filterResourceId (index order) and the date windows keep their own index order."
|
|
22493
|
+
},
|
|
22475
22494
|
"filterCreatedFrom": {
|
|
22476
22495
|
"type": "string",
|
|
22477
22496
|
"description": "Filters results to include only those created from the specified date and time. The value must be in ISO 8601 format."
|
|
@@ -22546,7 +22565,7 @@
|
|
|
22546
22565
|
"properties": {
|
|
22547
22566
|
"resourceId": {
|
|
22548
22567
|
"type": "string",
|
|
22549
|
-
"description": "Identifier of the resource this report is associated with (job
|
|
22568
|
+
"description": "Identifier of the resource this report is associated with: the tenant id for the scheduled tenant reports (resourceType tenants), a job id for a job report. On the wire since 2026-09-24 (it was stored but not returned)."
|
|
22550
22569
|
},
|
|
22551
22570
|
"resourceType": {
|
|
22552
22571
|
"type": "string",
|
|
@@ -22573,7 +22592,7 @@
|
|
|
22573
22592
|
},
|
|
22574
22593
|
"settings": {
|
|
22575
22594
|
"type": "string",
|
|
22576
|
-
"description": "
|
|
22595
|
+
"description": "The analysis window the broker stamps at creation (startDate, endDate, reportPeriod, displayName and the period's own fields such as isoWeek or monthName). Since 2026-09-24 (PLAN_TENANT_SETTINGS_CLEANUP) no `emails`: reports are downloaded in the report app, not mailed."
|
|
22577
22596
|
},
|
|
22578
22597
|
"shortCode": {
|
|
22579
22598
|
"type": "string",
|
|
@@ -22713,7 +22732,7 @@
|
|
|
22713
22732
|
"properties": {
|
|
22714
22733
|
"resourceId": {
|
|
22715
22734
|
"type": "string",
|
|
22716
|
-
"description": "Identifier of the resource this report is associated with (job
|
|
22735
|
+
"description": "Identifier of the resource this report is associated with: the tenant id for the scheduled tenant reports (resourceType tenants), a job id for a job report. On the wire since 2026-09-24 (it was stored but not returned)."
|
|
22717
22736
|
},
|
|
22718
22737
|
"resourceType": {
|
|
22719
22738
|
"type": "string",
|
|
@@ -22740,7 +22759,7 @@
|
|
|
22740
22759
|
},
|
|
22741
22760
|
"settings": {
|
|
22742
22761
|
"type": "string",
|
|
22743
|
-
"description": "
|
|
22762
|
+
"description": "The analysis window the broker stamps at creation (startDate, endDate, reportPeriod, displayName and the period's own fields such as isoWeek or monthName). Since 2026-09-24 (PLAN_TENANT_SETTINGS_CLEANUP) no `emails`: reports are downloaded in the report app, not mailed."
|
|
22744
22763
|
},
|
|
22745
22764
|
"shortCode": {
|
|
22746
22765
|
"type": "string",
|