@smartytalent/mcp-tools 0.9.53 → 0.9.55

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/dist/tools.json +198 -20
  2. package/package.json +1 -1
package/dist/tools.json CHANGED
@@ -202,7 +202,7 @@
202
202
  "automation": {
203
203
  "title": "TenantAttributesSettingsAutomationSchema",
204
204
  "type": "object",
205
- "description": "The organisation's DEFAULT automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24), the same seven keys and values as job.settings.automation: auto = Boe runs the stage, manual = a human runs it (a task on the RecOps board), off = the stage is not part of the process. A job overrides these in BOTH directions (a tenant on manual pilots auto on one job); absent = the platform default (sourcing manual, everything else auto). PATCH merges this block PER KEY (a key sent as null clears the default). Validated in code like the job block: interview and offer accept auto|manual, surveys accepts auto|off, the rest auto|manual|off. NOTE: the generated model whitelists keys, so this property MUST be declared for the SDK to carry it.",
205
+ "description": "The organisation's DEFAULT automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24), the same eight keys and values as job.settings.automation: auto = Boe runs the stage, manual = a human runs it (a task on the RecOps board), off = the stage is not part of the process. A job overrides these in BOTH directions (a tenant on manual pilots auto on one job); absent = the platform default (sourcing manual, everything else auto). This block is where an organisation's process PROFILE lives, e.g. 'screening only' (stage 3, 2026-10-06): every key off except the CV screening, advertising off. PATCH merges this block PER KEY (several keys in one PATCH are fine; a key sent as null clears that default). Validated in code like the job block: every key accepts auto|manual|off (S.K. 2026-10-06: no exceptions); an unknown key or value is a 400 naming it. Writable through the tenant PATCH (sysowner / owner / admin). NOTE: the generated model whitelists keys, so this property MUST be declared for the SDK to carry it.",
206
206
  "properties": {
207
207
  "sourcing": {
208
208
  "type": "string",
@@ -218,19 +218,23 @@
218
218
  },
219
219
  "interview": {
220
220
  "type": "string",
221
- "description": "auto | manual"
221
+ "description": "auto | manual | off (off since 2026-10-06)"
222
222
  },
223
223
  "offer": {
224
224
  "type": "string",
225
- "description": "auto | manual"
225
+ "description": "auto | manual | off (off since 2026-10-06)"
226
226
  },
227
227
  "surveys": {
228
228
  "type": "string",
229
- "description": "auto | off"
229
+ "description": "auto | manual | off (manual since 2026-10-06)"
230
230
  },
231
231
  "feedback": {
232
232
  "type": "string",
233
233
  "description": "auto | manual | off"
234
+ },
235
+ "advertising": {
236
+ "type": "string",
237
+ "description": "auto | manual | off (new 2026-10-06; absent = auto). The job's ads and its public apply page, see job.settings.automation.advertising."
234
238
  }
235
239
  }
236
240
  },
@@ -779,7 +783,7 @@
779
783
  "automation": {
780
784
  "title": "TenantAttributesSettingsAutomationSchema",
781
785
  "type": "object",
782
- "description": "The organisation's DEFAULT automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24), the same seven keys and values as job.settings.automation: auto = Boe runs the stage, manual = a human runs it (a task on the RecOps board), off = the stage is not part of the process. A job overrides these in BOTH directions (a tenant on manual pilots auto on one job); absent = the platform default (sourcing manual, everything else auto). PATCH merges this block PER KEY (a key sent as null clears the default). Validated in code like the job block: interview and offer accept auto|manual, surveys accepts auto|off, the rest auto|manual|off. NOTE: the generated model whitelists keys, so this property MUST be declared for the SDK to carry it.",
786
+ "description": "The organisation's DEFAULT automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24), the same eight keys and values as job.settings.automation: auto = Boe runs the stage, manual = a human runs it (a task on the RecOps board), off = the stage is not part of the process. A job overrides these in BOTH directions (a tenant on manual pilots auto on one job); absent = the platform default (sourcing manual, everything else auto). This block is where an organisation's process PROFILE lives, e.g. 'screening only' (stage 3, 2026-10-06): every key off except the CV screening, advertising off. PATCH merges this block PER KEY (several keys in one PATCH are fine; a key sent as null clears that default). Validated in code like the job block: every key accepts auto|manual|off (S.K. 2026-10-06: no exceptions); an unknown key or value is a 400 naming it. Writable through the tenant PATCH (sysowner / owner / admin). NOTE: the generated model whitelists keys, so this property MUST be declared for the SDK to carry it.",
783
787
  "properties": {
784
788
  "sourcing": {
785
789
  "type": "string",
@@ -795,19 +799,23 @@
795
799
  },
796
800
  "interview": {
797
801
  "type": "string",
798
- "description": "auto | manual"
802
+ "description": "auto | manual | off (off since 2026-10-06)"
799
803
  },
800
804
  "offer": {
801
805
  "type": "string",
802
- "description": "auto | manual"
806
+ "description": "auto | manual | off (off since 2026-10-06)"
803
807
  },
804
808
  "surveys": {
805
809
  "type": "string",
806
- "description": "auto | off"
810
+ "description": "auto | manual | off (manual since 2026-10-06)"
807
811
  },
808
812
  "feedback": {
809
813
  "type": "string",
810
814
  "description": "auto | manual | off"
815
+ },
816
+ "advertising": {
817
+ "type": "string",
818
+ "description": "auto | manual | off (new 2026-10-06; absent = auto). The job's ads and its public apply page, see job.settings.automation.advertising."
811
819
  }
812
820
  }
813
821
  },
@@ -4213,6 +4221,60 @@
4213
4221
  "timestamp": {
4214
4222
  "type": "string",
4215
4223
  "description": "ISO 8601 time the consent was recorded."
4224
+ },
4225
+ "currentProof": {
4226
+ "title": "TalentConsentProofSchema",
4227
+ "type": "object",
4228
+ "description": "The proof of a consent (stage 3, 2026-10-06): the privacy notice the candidate was shown and when.\n`currentProof` = the latest application's consent to its recruitment; `futureProof` = the latest consent\nto future recruitments (kept as evidence when the consent is withdrawn later).",
4229
+ "properties": {
4230
+ "version": {
4231
+ "type": "integer"
4232
+ },
4233
+ "hash": {
4234
+ "type": "string",
4235
+ "description": "sha256:<64 hex> of the notice's text in `language` (tenants/{shortCode}/privacy/v{version}.json)."
4236
+ },
4237
+ "language": {
4238
+ "type": "string"
4239
+ },
4240
+ "at": {
4241
+ "type": "string",
4242
+ "format": "date-time"
4243
+ },
4244
+ "submissionId": {
4245
+ "type": "string"
4246
+ },
4247
+ "jobId": {
4248
+ "type": "string"
4249
+ }
4250
+ }
4251
+ },
4252
+ "futureProof": {
4253
+ "title": "TalentConsentProofSchema",
4254
+ "type": "object",
4255
+ "description": "The proof of a consent (stage 3, 2026-10-06): the privacy notice the candidate was shown and when.\n`currentProof` = the latest application's consent to its recruitment; `futureProof` = the latest consent\nto future recruitments (kept as evidence when the consent is withdrawn later).",
4256
+ "properties": {
4257
+ "version": {
4258
+ "type": "integer"
4259
+ },
4260
+ "hash": {
4261
+ "type": "string",
4262
+ "description": "sha256:<64 hex> of the notice's text in `language` (tenants/{shortCode}/privacy/v{version}.json)."
4263
+ },
4264
+ "language": {
4265
+ "type": "string"
4266
+ },
4267
+ "at": {
4268
+ "type": "string",
4269
+ "format": "date-time"
4270
+ },
4271
+ "submissionId": {
4272
+ "type": "string"
4273
+ },
4274
+ "jobId": {
4275
+ "type": "string"
4276
+ }
4277
+ }
4216
4278
  }
4217
4279
  }
4218
4280
  },
@@ -4885,6 +4947,60 @@
4885
4947
  "timestamp": {
4886
4948
  "type": "string",
4887
4949
  "description": "ISO 8601 time the consent was recorded."
4950
+ },
4951
+ "currentProof": {
4952
+ "title": "TalentConsentProofSchema",
4953
+ "type": "object",
4954
+ "description": "The proof of a consent (stage 3, 2026-10-06): the privacy notice the candidate was shown and when.\n`currentProof` = the latest application's consent to its recruitment; `futureProof` = the latest consent\nto future recruitments (kept as evidence when the consent is withdrawn later).",
4955
+ "properties": {
4956
+ "version": {
4957
+ "type": "integer"
4958
+ },
4959
+ "hash": {
4960
+ "type": "string",
4961
+ "description": "sha256:<64 hex> of the notice's text in `language` (tenants/{shortCode}/privacy/v{version}.json)."
4962
+ },
4963
+ "language": {
4964
+ "type": "string"
4965
+ },
4966
+ "at": {
4967
+ "type": "string",
4968
+ "format": "date-time"
4969
+ },
4970
+ "submissionId": {
4971
+ "type": "string"
4972
+ },
4973
+ "jobId": {
4974
+ "type": "string"
4975
+ }
4976
+ }
4977
+ },
4978
+ "futureProof": {
4979
+ "title": "TalentConsentProofSchema",
4980
+ "type": "object",
4981
+ "description": "The proof of a consent (stage 3, 2026-10-06): the privacy notice the candidate was shown and when.\n`currentProof` = the latest application's consent to its recruitment; `futureProof` = the latest consent\nto future recruitments (kept as evidence when the consent is withdrawn later).",
4982
+ "properties": {
4983
+ "version": {
4984
+ "type": "integer"
4985
+ },
4986
+ "hash": {
4987
+ "type": "string",
4988
+ "description": "sha256:<64 hex> of the notice's text in `language` (tenants/{shortCode}/privacy/v{version}.json)."
4989
+ },
4990
+ "language": {
4991
+ "type": "string"
4992
+ },
4993
+ "at": {
4994
+ "type": "string",
4995
+ "format": "date-time"
4996
+ },
4997
+ "submissionId": {
4998
+ "type": "string"
4999
+ },
5000
+ "jobId": {
5001
+ "type": "string"
5002
+ }
5003
+ }
4888
5004
  }
4889
5005
  }
4890
5006
  },
@@ -5202,11 +5318,19 @@
5202
5318
  },
5203
5319
  "applyPage": {
5204
5320
  "type": "object",
5205
- "description": "Package 8 (2026-10-05): the public application page of the job, stamped at every publication (a public job at its activation, a confidential or internal one when RecOps shared it). Absent = not published.",
5321
+ "description": "Package 8 (2026-10-05): the public application page of the job, stamped at every publication (a public job at its activation, a confidential or internal one when RecOps shared it, a form-only page when RecOps shared the full one). Absent = not published.",
5206
5322
  "properties": {
5207
5323
  "url": {
5208
5324
  "type": "string",
5209
- "description": "The page's public address, https://apply.{domain}/{language tag}/{tenant short code}/{job short code}."
5325
+ "description": "Where a candidate lands: the full page https://apply.{domain}/{language tag}/{tenant short code}/{job short code}, or the form address (formUrl) when the page is published form only."
5326
+ },
5327
+ "formUrl": {
5328
+ "type": "string",
5329
+ "description": "The form-only address of the same page, https://apply.{domain}/{language tag}/{tenant short code}/{job short code}/form (stage 3, 2026-10-06): present on every page published since, the link RecOps copies for a form-only job."
5330
+ },
5331
+ "formOnly": {
5332
+ "type": "boolean",
5333
+ "description": "true when this publication is FORM ONLY (stage 3, 2026-10-06): the job's settings.automation.advertising is off, or manual and RecOps has not shared the full page yet. The public data then carries no ad content (no copy, no images), the job is not on the careers listing and the full address redirects to the form. false or absent = the full page."
5210
5334
  },
5211
5335
  "publishedAt": {
5212
5336
  "type": "string",
@@ -5690,7 +5814,7 @@
5690
5814
  "automation": {
5691
5815
  "title": "JobAttributesSettingsAutomationSchema",
5692
5816
  "type": "object",
5693
- "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).",
5817
+ "description": "Per-job automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24): who runs each stage of THIS recruitment process. Values per key, the same three for every key (S.K. 2026-10-06): 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. For sourcing / screeningCall / assessment off means the candidate moves on to the next stage the process has; for interview / offer off means the process ends before that stage and the candidate stays where they are, with the verdict. 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. A job whose phone screening, assessment, interview and offer are all effectively off is a 'screening only' process (stage 3, 2026-10-06): Boe screens the CV and stops (no phone screening, assessment, interview ask or offer, no rejection on the verdict), RecOps is notified of every verdict and decides. That is not a stored key: it is derived from the four keys (automation:resolve output screeningOnly), so a UI tile sets the keys. Read by the automation:resolve action at the head of the candidate-facing workflows, by feedback:resolve (feedback), by the ad build and by the apply page publication (advertising). PATCH merges this block PER KEY: several keys in one PATCH are fine, a key sent as null clears that override (a client model that serialises every unset key as null clears them all; build the request with only the keys you mean). 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: every key accepts 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); a brief whose job is built while assessment is off builds no assessment.",
5694
5818
  "properties": {
5695
5819
  "sourcing": {
5696
5820
  "type": "string",
@@ -5706,19 +5830,23 @@
5706
5830
  },
5707
5831
  "interview": {
5708
5832
  "type": "string",
5709
- "description": "auto | manual. The HM consent ask and the autonomous interview booking: manual = no HM e-mail, no booking, a board task, the candidate stays at interview (the shortlist). No off in v1."
5833
+ "description": "auto | manual | off. The HM consent ask and the autonomous interview booking: manual = no HM e-mail, no booking, a board task, the candidate stays at interview (the shortlist); off (2026-10-06) = the process ends before the interview: a candidate who passed the earlier stages stays at the stage they reached, with the verdict, and is never moved to interview by Boe; no HM e-mail, no booking, no board task. A candidate a human moves to interview anyway gets no HM ask either (a note says the stage is off)."
5710
5834
  },
5711
5835
  "offer": {
5712
5836
  "type": "string",
5713
- "description": "auto | manual. After the HM's yes: auto = offer document draft + congratulation e-mail, manual = the stage move and the audit note only, plus a board task. No off in v1."
5837
+ "description": "auto | manual | off. After the HM's yes: auto = offer document draft + congratulation e-mail, manual = the stage move and the audit note only, plus a board task; off (2026-10-06) = the process ends before the offer: the HM's yes is noted on the candidate, who stays at interview; no offer draft, no e-mail, no stage move, no board task."
5714
5838
  },
5715
5839
  "surveys": {
5716
5840
  "type": "string",
5717
- "description": "auto | off. cNPS surveys: off = no survey invitation after a hire and no survey link in rejection e-mails."
5841
+ "description": "auto | manual | off. cNPS surveys: auto = Boe sends the survey invitation after a hire and rejection e-mails carry the survey link; manual (2026-10-06) = Boe sends no survey: one board task per hire (send the survey yourself) and no survey link in rejection e-mails; off = no survey invitation after a hire and no survey link in rejection e-mails."
5718
5842
  },
5719
5843
  "feedback": {
5720
5844
  "type": "string",
5721
5845
  "description": "auto | manual | off. Candidate feedback e-mails the feedback policy allows: auto = composed, scheduled and sent by the workflow, manual = composed by Boe and HELD as a draft in the candidate's thread with a board task, released by the operator's emails:send order, off = no feedback e-mail."
5846
+ },
5847
+ "advertising": {
5848
+ "type": "string",
5849
+ "description": "auto | manual | off (new 2026-10-06; absent everywhere = auto). The job's ads and its public apply page. auto = the ads are built as drafts at the job build, accepted at the activation, and the full apply page and the careers listing entry go up with them (today's behaviour). manual = the ads are built as drafts, the activation publishes the page FORM ONLY (applyPage.formOnly, not on the careers listing), the ads stay drafts and one board task asks RecOps; RecOps publishes the full page and the listing entry with the share order (jobs:activate with meta.publishApply on the active job); a later re-activation publishes the form only again. off = no ads are built (neither at the job build nor at the activation) and the page is published form only. No code posts to job boards: RecOps copies the built ads by hand."
5722
5850
  }
5723
5851
  }
5724
5852
  }
@@ -6170,11 +6298,19 @@
6170
6298
  },
6171
6299
  "applyPage": {
6172
6300
  "type": "object",
6173
- "description": "Package 8 (2026-10-05): the public application page of the job, stamped at every publication (a public job at its activation, a confidential or internal one when RecOps shared it). Absent = not published.",
6301
+ "description": "Package 8 (2026-10-05): the public application page of the job, stamped at every publication (a public job at its activation, a confidential or internal one when RecOps shared it, a form-only page when RecOps shared the full one). Absent = not published.",
6174
6302
  "properties": {
6175
6303
  "url": {
6176
6304
  "type": "string",
6177
- "description": "The page's public address, https://apply.{domain}/{language tag}/{tenant short code}/{job short code}."
6305
+ "description": "Where a candidate lands: the full page https://apply.{domain}/{language tag}/{tenant short code}/{job short code}, or the form address (formUrl) when the page is published form only."
6306
+ },
6307
+ "formUrl": {
6308
+ "type": "string",
6309
+ "description": "The form-only address of the same page, https://apply.{domain}/{language tag}/{tenant short code}/{job short code}/form (stage 3, 2026-10-06): present on every page published since, the link RecOps copies for a form-only job."
6310
+ },
6311
+ "formOnly": {
6312
+ "type": "boolean",
6313
+ "description": "true when this publication is FORM ONLY (stage 3, 2026-10-06): the job's settings.automation.advertising is off, or manual and RecOps has not shared the full page yet. The public data then carries no ad content (no copy, no images), the job is not on the careers listing and the full address redirects to the form. false or absent = the full page."
6178
6314
  },
6179
6315
  "publishedAt": {
6180
6316
  "type": "string",
@@ -6658,7 +6794,7 @@
6658
6794
  "automation": {
6659
6795
  "title": "JobAttributesSettingsAutomationSchema",
6660
6796
  "type": "object",
6661
- "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).",
6797
+ "description": "Per-job automation switches (PLAN_PROCESS_AUTOMATION, 2026-09-24): who runs each stage of THIS recruitment process. Values per key, the same three for every key (S.K. 2026-10-06): 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. For sourcing / screeningCall / assessment off means the candidate moves on to the next stage the process has; for interview / offer off means the process ends before that stage and the candidate stays where they are, with the verdict. 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. A job whose phone screening, assessment, interview and offer are all effectively off is a 'screening only' process (stage 3, 2026-10-06): Boe screens the CV and stops (no phone screening, assessment, interview ask or offer, no rejection on the verdict), RecOps is notified of every verdict and decides. That is not a stored key: it is derived from the four keys (automation:resolve output screeningOnly), so a UI tile sets the keys. Read by the automation:resolve action at the head of the candidate-facing workflows, by feedback:resolve (feedback), by the ad build and by the apply page publication (advertising). PATCH merges this block PER KEY: several keys in one PATCH are fine, a key sent as null clears that override (a client model that serialises every unset key as null clears them all; build the request with only the keys you mean). 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: every key accepts 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); a brief whose job is built while assessment is off builds no assessment.",
6662
6798
  "properties": {
6663
6799
  "sourcing": {
6664
6800
  "type": "string",
@@ -6674,19 +6810,23 @@
6674
6810
  },
6675
6811
  "interview": {
6676
6812
  "type": "string",
6677
- "description": "auto | manual. The HM consent ask and the autonomous interview booking: manual = no HM e-mail, no booking, a board task, the candidate stays at interview (the shortlist). No off in v1."
6813
+ "description": "auto | manual | off. The HM consent ask and the autonomous interview booking: manual = no HM e-mail, no booking, a board task, the candidate stays at interview (the shortlist); off (2026-10-06) = the process ends before the interview: a candidate who passed the earlier stages stays at the stage they reached, with the verdict, and is never moved to interview by Boe; no HM e-mail, no booking, no board task. A candidate a human moves to interview anyway gets no HM ask either (a note says the stage is off)."
6678
6814
  },
6679
6815
  "offer": {
6680
6816
  "type": "string",
6681
- "description": "auto | manual. After the HM's yes: auto = offer document draft + congratulation e-mail, manual = the stage move and the audit note only, plus a board task. No off in v1."
6817
+ "description": "auto | manual | off. After the HM's yes: auto = offer document draft + congratulation e-mail, manual = the stage move and the audit note only, plus a board task; off (2026-10-06) = the process ends before the offer: the HM's yes is noted on the candidate, who stays at interview; no offer draft, no e-mail, no stage move, no board task."
6682
6818
  },
6683
6819
  "surveys": {
6684
6820
  "type": "string",
6685
- "description": "auto | off. cNPS surveys: off = no survey invitation after a hire and no survey link in rejection e-mails."
6821
+ "description": "auto | manual | off. cNPS surveys: auto = Boe sends the survey invitation after a hire and rejection e-mails carry the survey link; manual (2026-10-06) = Boe sends no survey: one board task per hire (send the survey yourself) and no survey link in rejection e-mails; off = no survey invitation after a hire and no survey link in rejection e-mails."
6686
6822
  },
6687
6823
  "feedback": {
6688
6824
  "type": "string",
6689
6825
  "description": "auto | manual | off. Candidate feedback e-mails the feedback policy allows: auto = composed, scheduled and sent by the workflow, manual = composed by Boe and HELD as a draft in the candidate's thread with a board task, released by the operator's emails:send order, off = no feedback e-mail."
6826
+ },
6827
+ "advertising": {
6828
+ "type": "string",
6829
+ "description": "auto | manual | off (new 2026-10-06; absent everywhere = auto). The job's ads and its public apply page. auto = the ads are built as drafts at the job build, accepted at the activation, and the full apply page and the careers listing entry go up with them (today's behaviour). manual = the ads are built as drafts, the activation publishes the page FORM ONLY (applyPage.formOnly, not on the careers listing), the ads stay drafts and one board task asks RecOps; RecOps publishes the full page and the listing entry with the share order (jobs:activate with meta.publishApply on the active job); a later re-activation publishes the form only again. off = no ads are built (neither at the job build nor at the activation) and the page is published form only. No code posts to job boards: RecOps copies the built ads by hand."
6690
6830
  }
6691
6831
  }
6692
6832
  }
@@ -6914,6 +7054,10 @@
6914
7054
  "pageBefore": {
6915
7055
  "type": "string",
6916
7056
  "description": "Returns the data encoded in Base64 format, used for cursor-based pagination"
7057
+ },
7058
+ "sort": {
7059
+ "type": "string",
7060
+ "description": "Order of the list. Leading `-` means descending.\n `-created` / `created` / `-modified` / `modified`: by time, as on the other lists.\n `-overallMatchRating`: the best rated first (stage 3, 2026-10-06): the band of the CV\n verdict (overallMatchRating, 1-5), then the verdict's score (meta.verdict.score), then\n the newest first, then the candidate id. Candidates without a rating come last.\n `overallMatchRating`: the rated candidates in the reverse order, those without a\n rating still last.\nThe rating order needs `filterJobId` (a 400 without it): the job's candidates are read\nwhole and ordered before the page is cut, so the order is stable across pages, with\npageNumber / pageSize (exact totals) or the cursor links of the answer."
6917
7061
  }
6918
7062
  }
6919
7063
  },
@@ -13481,12 +13625,29 @@
13481
13625
  },
13482
13626
  "consent": {
13483
13627
  "type": "object",
13628
+ "description": "The candidate's consents at submission (stage 3, 2026-10-06). `current` = this recruitment, `future` =\nfuture recruitments (the talent pool). The guest door stores the PROOF of the privacy notice the\ncandidate was shown: `version`, `hash` (that notice's hashes[language]), `language` and `at` (server\ntime); `legacy: true` = a submission without the proof, accepted before the environment enforces it.\nThe talent takes the proof over (TalentConsentSchema.currentProof / futureProof).",
13484
13629
  "properties": {
13485
13630
  "current": {
13486
13631
  "type": "boolean"
13487
13632
  },
13488
13633
  "future": {
13489
13634
  "type": "boolean"
13635
+ },
13636
+ "version": {
13637
+ "type": "integer"
13638
+ },
13639
+ "hash": {
13640
+ "type": "string"
13641
+ },
13642
+ "language": {
13643
+ "type": "string"
13644
+ },
13645
+ "at": {
13646
+ "type": "string",
13647
+ "format": "date-time"
13648
+ },
13649
+ "legacy": {
13650
+ "type": "boolean"
13490
13651
  }
13491
13652
  }
13492
13653
  },
@@ -14005,12 +14166,29 @@
14005
14166
  },
14006
14167
  "consent": {
14007
14168
  "type": "object",
14169
+ "description": "The candidate's consents at submission (stage 3, 2026-10-06). `current` = this recruitment, `future` =\nfuture recruitments (the talent pool). The guest door stores the PROOF of the privacy notice the\ncandidate was shown: `version`, `hash` (that notice's hashes[language]), `language` and `at` (server\ntime); `legacy: true` = a submission without the proof, accepted before the environment enforces it.\nThe talent takes the proof over (TalentConsentSchema.currentProof / futureProof).",
14008
14170
  "properties": {
14009
14171
  "current": {
14010
14172
  "type": "boolean"
14011
14173
  },
14012
14174
  "future": {
14013
14175
  "type": "boolean"
14176
+ },
14177
+ "version": {
14178
+ "type": "integer"
14179
+ },
14180
+ "hash": {
14181
+ "type": "string"
14182
+ },
14183
+ "language": {
14184
+ "type": "string"
14185
+ },
14186
+ "at": {
14187
+ "type": "string",
14188
+ "format": "date-time"
14189
+ },
14190
+ "legacy": {
14191
+ "type": "boolean"
14014
14192
  }
14015
14193
  }
14016
14194
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@smartytalent/mcp-tools",
3
- "version": "0.9.53",
3
+ "version": "0.9.55",
4
4
  "description": "MCP tool definitions for SmartyTalent API",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",