@smartytalent/mcp-tools 0.9.42 → 0.9.44

package/dist/tools.json

@@ -297,7 +297,7 @@
                     "language": {
                       "type": "string",
                       "pattern": "^[a-z]{2}-[A-Z]{2}$",
-                      "description": "THE ORGANISATION'S OWN LANGUAGE - the tenant-level default\nevery surface falls back to when nothing more specific says\notherwise. BCP-47 (`pl-PL`, not `pl`). Supported today:\nen-US, pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB\n(British English; en-US stays the canonical storage locale),\nar-AE (Modern Standard Arabic).\n\nDistinct from `activeLanguages`, which is an UNORDERED SET of\nthe locales a tenant publishes in and carries no notion of a\nprimary one - never read `activeLanguages[0]` as the default.\nAlso distinct from a user's Cognito `locale`, which is one\nrecruiter's interface language.\n\nRead by the outbound-email locale chain, conversation\nlanguage, meeting lobby locale and careers `sourceLanguage`\nat create; NOT the translation target of the entity AI paths\n(file / talent / persona / timeline / report translate into the\npair's extra language). Onboarding seeds every new user's\nCognito locale from it.\n\nClient-writable through tenant create/PATCH (settings merge\nis shallow, so sending only `language` preserves the other\nsettings keys). CHECKED on write (PLAN_TENANT_LANGUAGES,\n2026-09-25): a platform locale that is one of the tenant's\n`activeLanguages`, else a 400; missing at create = en-US.\nChanging it does NOT change `activeLanguages`. The entity AI\npipelines translate into the pair's extra language, not into\nthis default."
+                      "description": "THE ORGANISATION'S OWN LANGUAGE - the tenant-level default\nevery surface falls back to when nothing more specific says\notherwise. BCP-47 (`pl-PL`, not `pl`). Supported today:\nen-US, pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB\n(British English; en-US stays the canonical storage locale),\nar-AE (Modern Standard Arabic), es-ES (European Spanish) -\nexactly these ten; another region of a language (es-MX,\nar-SA) is another language and is refused.\n\nDistinct from `activeLanguages`, which is an UNORDERED SET of\nthe locales a tenant publishes in and carries no notion of a\nprimary one - never read `activeLanguages[0]` as the default.\nAlso distinct from a user's Cognito `locale`, which is one\nrecruiter's interface language.\n\nRead by the outbound-email locale chain, conversation\nlanguage, meeting lobby locale and careers `sourceLanguage`\nat create; NOT the translation target of the entity AI paths\n(file / talent / persona / timeline / report translate into the\npair's extra language). Onboarding seeds every new user's\nCognito locale from it.\n\nClient-writable through tenant create/PATCH (settings merge\nis shallow, so sending only `language` preserves the other\nsettings keys). CHECKED on write (PLAN_TENANT_LANGUAGES,\n2026-09-25): a platform locale that is one of the tenant's\n`activeLanguages`, else a 400; missing at create = en-US.\nChanging it does NOT change `activeLanguages`. The entity AI\npipelines translate into the pair's extra language, not into\nthis default."
                     },
                     "calling": {
                       "type": "object",
@@ -468,7 +468,7 @@
                 },
                 "activeLanguages": {
                   "type": "array",
-                  "description": "The tenant's SUPPORTED-LANGUAGE PAIR: the system language en-US plus AT MOST ONE more - [en-US] or [en-US, X], X one of pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB, ar-AE (PLAN_TENANT_LANGUAGES, 2026-09-25; ar-AE since PLAN_LANGUAGE_AR_AE). Set when the organisation is created (omitted = [en-US] plus settings.language when that is not en-US); afterwards only a system owner may change it - any other role may re-send the same pair (any order) and gets a 400 for a different one. settings.language (the default) must be one of these; the entity AI pipelines translate into X. Checked by the server, not by schema constraints: a generated client must still read a legacy row (e.g. [] or ['pl']) until the data fix reaches it. A TOP-LEVEL tenant attribute - never inside settings.",
+                  "description": "The tenant's SUPPORTED-LANGUAGE PAIR: the system language en-US plus AT MOST ONE more - [en-US] or [en-US, X], X one of pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB, ar-AE, es-ES (PLAN_TENANT_LANGUAGES, 2026-09-25; ar-AE since PLAN_LANGUAGE_AR_AE, es-ES since PLAN_LANGUAGE_ES_ES). Set when the organisation is created (omitted = [en-US] plus settings.language when that is not en-US); afterwards only a system owner may change it - any other role may re-send the same pair (any order) and gets a 400 for a different one. settings.language (the default) must be one of these; the entity AI pipelines translate into X. Checked by the server, not by schema constraints: a generated client must still read a legacy row (e.g. [] or ['pl']) until the data fix reaches it. A TOP-LEVEL tenant attribute - never inside settings.",
                   "items": {
                     "type": "string",
                     "pattern": "^[a-z]{2}-[A-Z]{2}$"
@@ -874,7 +874,7 @@
                     "language": {
                       "type": "string",
                       "pattern": "^[a-z]{2}-[A-Z]{2}$",
-                      "description": "THE ORGANISATION'S OWN LANGUAGE - the tenant-level default\nevery surface falls back to when nothing more specific says\notherwise. BCP-47 (`pl-PL`, not `pl`). Supported today:\nen-US, pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB\n(British English; en-US stays the canonical storage locale),\nar-AE (Modern Standard Arabic).\n\nDistinct from `activeLanguages`, which is an UNORDERED SET of\nthe locales a tenant publishes in and carries no notion of a\nprimary one - never read `activeLanguages[0]` as the default.\nAlso distinct from a user's Cognito `locale`, which is one\nrecruiter's interface language.\n\nRead by the outbound-email locale chain, conversation\nlanguage, meeting lobby locale and careers `sourceLanguage`\nat create; NOT the translation target of the entity AI paths\n(file / talent / persona / timeline / report translate into the\npair's extra language). Onboarding seeds every new user's\nCognito locale from it.\n\nClient-writable through tenant create/PATCH (settings merge\nis shallow, so sending only `language` preserves the other\nsettings keys). CHECKED on write (PLAN_TENANT_LANGUAGES,\n2026-09-25): a platform locale that is one of the tenant's\n`activeLanguages`, else a 400; missing at create = en-US.\nChanging it does NOT change `activeLanguages`. The entity AI\npipelines translate into the pair's extra language, not into\nthis default."
+                      "description": "THE ORGANISATION'S OWN LANGUAGE - the tenant-level default\nevery surface falls back to when nothing more specific says\notherwise. BCP-47 (`pl-PL`, not `pl`). Supported today:\nen-US, pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB\n(British English; en-US stays the canonical storage locale),\nar-AE (Modern Standard Arabic), es-ES (European Spanish) -\nexactly these ten; another region of a language (es-MX,\nar-SA) is another language and is refused.\n\nDistinct from `activeLanguages`, which is an UNORDERED SET of\nthe locales a tenant publishes in and carries no notion of a\nprimary one - never read `activeLanguages[0]` as the default.\nAlso distinct from a user's Cognito `locale`, which is one\nrecruiter's interface language.\n\nRead by the outbound-email locale chain, conversation\nlanguage, meeting lobby locale and careers `sourceLanguage`\nat create; NOT the translation target of the entity AI paths\n(file / talent / persona / timeline / report translate into the\npair's extra language). Onboarding seeds every new user's\nCognito locale from it.\n\nClient-writable through tenant create/PATCH (settings merge\nis shallow, so sending only `language` preserves the other\nsettings keys). CHECKED on write (PLAN_TENANT_LANGUAGES,\n2026-09-25): a platform locale that is one of the tenant's\n`activeLanguages`, else a 400; missing at create = en-US.\nChanging it does NOT change `activeLanguages`. The entity AI\npipelines translate into the pair's extra language, not into\nthis default."
                     },
                     "calling": {
                       "type": "object",
@@ -1045,7 +1045,7 @@
                 },
                 "activeLanguages": {
                   "type": "array",
-                  "description": "The tenant's SUPPORTED-LANGUAGE PAIR: the system language en-US plus AT MOST ONE more - [en-US] or [en-US, X], X one of pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB, ar-AE (PLAN_TENANT_LANGUAGES, 2026-09-25; ar-AE since PLAN_LANGUAGE_AR_AE). Set when the organisation is created (omitted = [en-US] plus settings.language when that is not en-US); afterwards only a system owner may change it - any other role may re-send the same pair (any order) and gets a 400 for a different one. settings.language (the default) must be one of these; the entity AI pipelines translate into X. Checked by the server, not by schema constraints: a generated client must still read a legacy row (e.g. [] or ['pl']) until the data fix reaches it. A TOP-LEVEL tenant attribute - never inside settings.",
+                  "description": "The tenant's SUPPORTED-LANGUAGE PAIR: the system language en-US plus AT MOST ONE more - [en-US] or [en-US, X], X one of pl-PL, de-DE, it-IT, fr-FR, cs-CZ, he-IL, en-GB, ar-AE, es-ES (PLAN_TENANT_LANGUAGES, 2026-09-25; ar-AE since PLAN_LANGUAGE_AR_AE, es-ES since PLAN_LANGUAGE_ES_ES). Set when the organisation is created (omitted = [en-US] plus settings.language when that is not en-US); afterwards only a system owner may change it - any other role may re-send the same pair (any order) and gets a 400 for a different one. settings.language (the default) must be one of these; the entity AI pipelines translate into X. Checked by the server, not by schema constraints: a generated client must still read a legacy row (e.g. [] or ['pl']) until the data fix reaches it. A TOP-LEVEL tenant attribute - never inside settings.",
                   "items": {
                     "type": "string",
                     "pattern": "^[a-z]{2}-[A-Z]{2}$"
@@ -1725,11 +1725,12 @@
       "properties": {
         "filterStatus": {
           "type": "string",
-          "description": "Returns users with this status. Omitting it returns EVERY status - the server applies no default, so `pending` accounts already appear in an unfiltered list. `pending` is the approval queue: a JIT user provisioned through enterprise SSO lands there and holds no tenant claims at all until an owner or admin flips them to active.",
+          "description": "Returns users with this status. Omitting it returns every status EXCEPT `deleted` - the server applies no other default, so `pending` accounts already appear in an unfiltered list. `pending` is the approval queue: a JIT user provisioned through enterprise SSO lands there and holds no tenant claims at all until an owner or admin flips them to active. `deleted` (2026-09-28) lists the tombstones of permanently deleted users - the audit view; they never appear otherwise.",
           "enum": [
             "active",
             "archived",
-            "pending"
+            "pending",
+            "deleted"
           ]
         },
         "filterCreatedFrom": {
@@ -1816,7 +1817,7 @@
                 },
                 "locale": {
                   "type": "string",
-                  "description": "The user's language as a BCP-47 tag (the Cognito `locale`). British English is stored as the full `en-GB`, Arabic (Modern Standard, UAE) as `ar-AE` - every variant is its own language, `ar-SA` is not ar-AE; legacy 2-letter values (`en`, `pl`, ...) exist and mean the base locale (`en` = en-US). Clients derive their URL segment from it (`en-GB` -> `en-gb`, `ar-AE` -> `ar`, `he-IL` -> `he`)."
+                  "description": "The user's language as a BCP-47 tag (the Cognito `locale`). British English is stored as the full `en-GB`, Arabic (Modern Standard, UAE) as `ar-AE`, Spanish (Spain) as `es-ES` - every variant is its own language, `ar-SA` is not ar-AE and `es-MX` is not es-ES; legacy 2-letter values (`en`, `pl`, ...) exist and mean the base locale (`en` = en-US). Clients use the tag itself as the URL segment (`/en-GB/`, `/ar-AE/`, `/es-ES/`), a legacy value read through the canonical rule first (`pl` -> `pl-PL`, `en` -> `en-US`)."
                 },
                 "phone": {
                   "type": "string"
@@ -1923,7 +1924,8 @@
                   "description": "CREATE-ONLY. False (default): the account lands in FORCE_CHANGE_PASSWORD and the user must change the password at first sign-in. True: the password is permanent and the account is active immediately (audited)."
                 },
                 "status": {
-                  "type": "string"
+                  "type": "string",
+                  "description": "`active` or `archived` (the two a client may set: DELETE without a flag archives, PATCH status=active restores), `pending` (a JIT SSO account awaiting approval), or `deleted` - the TOMBSTONE (2026-09-28): a permanently deleted user keeps its row under the same id with the personal data cleared (name and email empty, no phone, address, avatar, settings, connections or history) and `meta.deletedAt`, `meta.deletedBy` (the deleting user's id) and `meta.deletedRole` (the role at deletion), so every job, note, comment and timeline entry that names the user keeps resolving; clients render it as a former user with the id prefix. A tombstone takes no PATCH (400), no second DELETE (400) and no invitation (400); GET /v1/users hides it unless `filterStatus=deleted`; its e-mail is free for a new account. Never settable by a client."
                 },
                 "historyEvents": {
                   "type": "array",
@@ -2165,7 +2167,7 @@
                 },
                 "locale": {
                   "type": "string",
-                  "description": "The user's language as a BCP-47 tag (the Cognito `locale`). British English is stored as the full `en-GB`, Arabic (Modern Standard, UAE) as `ar-AE` - every variant is its own language, `ar-SA` is not ar-AE; legacy 2-letter values (`en`, `pl`, ...) exist and mean the base locale (`en` = en-US). Clients derive their URL segment from it (`en-GB` -> `en-gb`, `ar-AE` -> `ar`, `he-IL` -> `he`)."
+                  "description": "The user's language as a BCP-47 tag (the Cognito `locale`). British English is stored as the full `en-GB`, Arabic (Modern Standard, UAE) as `ar-AE`, Spanish (Spain) as `es-ES` - every variant is its own language, `ar-SA` is not ar-AE and `es-MX` is not es-ES; legacy 2-letter values (`en`, `pl`, ...) exist and mean the base locale (`en` = en-US). Clients use the tag itself as the URL segment (`/en-GB/`, `/ar-AE/`, `/es-ES/`), a legacy value read through the canonical rule first (`pl` -> `pl-PL`, `en` -> `en-US`)."
                 },
                 "phone": {
                   "type": "string"
@@ -2272,7 +2274,8 @@
                   "description": "CREATE-ONLY. False (default): the account lands in FORCE_CHANGE_PASSWORD and the user must change the password at first sign-in. True: the password is permanent and the account is active immediately (audited)."
                 },
                 "status": {
-                  "type": "string"
+                  "type": "string",
+                  "description": "`active` or `archived` (the two a client may set: DELETE without a flag archives, PATCH status=active restores), `pending` (a JIT SSO account awaiting approval), or `deleted` - the TOMBSTONE (2026-09-28): a permanently deleted user keeps its row under the same id with the personal data cleared (name and email empty, no phone, address, avatar, settings, connections or history) and `meta.deletedAt`, `meta.deletedBy` (the deleting user's id) and `meta.deletedRole` (the role at deletion), so every job, note, comment and timeline entry that names the user keeps resolving; clients render it as a former user with the id prefix. A tombstone takes no PATCH (400), no second DELETE (400) and no invitation (400); GET /v1/users hides it unless `filterStatus=deleted`; its e-mail is free for a new account. Never settable by a client."
                 },
                 "historyEvents": {
                   "type": "array",
@@ -4398,7 +4401,8 @@
             "fr-FR",
             "cs-CZ",
             "en-GB",
-            "ar-AE"
+            "ar-AE",
+            "es-ES"
           ]
         }
       }
@@ -6006,7 +6010,8 @@
             "fr-FR",
             "cs-CZ",
             "en-GB",
-            "ar-AE"
+            "ar-AE",
+            "es-ES"
           ]
         }
       }
@@ -7438,7 +7443,8 @@
             "fr-FR",
             "cs-CZ",
             "en-GB",
-            "ar-AE"
+            "ar-AE",
+            "es-ES"
           ]
         }
       }
@@ -19906,8 +19912,8 @@
                 },
                 "defaultLocale": {
                   "type": "string",
-                  "pattern": "^(ar|cs|de|en|fr|he|it|pl)(-[A-Za-z0-9]{2,8})*$",
-                  "description": "Full BCP-47 locale tag (e.g. `en-US`, `pl-PL`, `fr-FR`, `ar-AE`, `he-IL`,\n`it-IT`). Set at creation time; controls the UI language of the\npublic lobby + room pages so a Polish recruiter sharing a link\ngets a Polish lobby regardless of the candidate's browser\nlanguage. Immutable after creation.\n\nNOT to be confused with `languageCode`: that field is auto-detected\nfrom the recorded speech and only populated post-meeting (AI\npipeline), whereas `defaultLocale` is human-picked at creation\ntime and drives UI.\n\nValidation: primary subtag must be one of {en, fr, ar, pl, it, cs};\nfull tags are accepted (en-US, pl-PL, ...). Default chain at\ncreation: request body -> tenant settings.language -> 'en-US'."
+                  "pattern": "^(ar|cs|de|en|es|fr|he|it|pl)(-[A-Za-z0-9]{2,8})*$",
+                  "description": "Full BCP-47 locale tag (e.g. `en-US`, `pl-PL`, `fr-FR`, `ar-AE`, `he-IL`,\n`es-ES`). Set at creation time; controls the UI language of the\npublic lobby + room pages so a Polish recruiter sharing a link\ngets a Polish lobby regardless of the candidate's browser\nlanguage. Immutable after creation.\n\nNOT to be confused with `languageCode`: that field is auto-detected\nfrom the recorded speech and only populated post-meeting (AI\npipeline), whereas `defaultLocale` is human-picked at creation\ntime and drives UI.\n\nValidation: the server accepts exactly the platform's ten locales\n(ar-AE, cs-CZ, de-DE, en-GB, en-US, es-ES, fr-FR, he-IL, it-IT,\npl-PL) and refuses any other tag with a 400; this pattern is wider\n(any tag whose primary subtag is a platform language) so a client\ncan still read a meeting written before. Default chain at\ncreation: request body -> tenant settings.language -> 'en-US'."
                 },
                 "meetingType": {
                   "type": "string",
@@ -20583,8 +20589,8 @@
                 },
                 "defaultLocale": {
                   "type": "string",
-                  "pattern": "^(ar|cs|de|en|fr|he|it|pl)(-[A-Za-z0-9]{2,8})*$",
-                  "description": "Full BCP-47 locale tag (e.g. `en-US`, `pl-PL`, `fr-FR`, `ar-AE`, `he-IL`,\n`it-IT`). Set at creation time; controls the UI language of the\npublic lobby + room pages so a Polish recruiter sharing a link\ngets a Polish lobby regardless of the candidate's browser\nlanguage. Immutable after creation.\n\nNOT to be confused with `languageCode`: that field is auto-detected\nfrom the recorded speech and only populated post-meeting (AI\npipeline), whereas `defaultLocale` is human-picked at creation\ntime and drives UI.\n\nValidation: primary subtag must be one of {en, fr, ar, pl, it, cs};\nfull tags are accepted (en-US, pl-PL, ...). Default chain at\ncreation: request body -> tenant settings.language -> 'en-US'."
+                  "pattern": "^(ar|cs|de|en|es|fr|he|it|pl)(-[A-Za-z0-9]{2,8})*$",
+                  "description": "Full BCP-47 locale tag (e.g. `en-US`, `pl-PL`, `fr-FR`, `ar-AE`, `he-IL`,\n`es-ES`). Set at creation time; controls the UI language of the\npublic lobby + room pages so a Polish recruiter sharing a link\ngets a Polish lobby regardless of the candidate's browser\nlanguage. Immutable after creation.\n\nNOT to be confused with `languageCode`: that field is auto-detected\nfrom the recorded speech and only populated post-meeting (AI\npipeline), whereas `defaultLocale` is human-picked at creation\ntime and drives UI.\n\nValidation: the server accepts exactly the platform's ten locales\n(ar-AE, cs-CZ, de-DE, en-GB, en-US, es-ES, fr-FR, he-IL, it-IT,\npl-PL) and refuses any other tag with a 400; this pattern is wider\n(any tag whose primary subtag is a platform language) so a client\ncan still read a meeting written before. Default chain at\ncreation: request body -> tenant settings.language -> 'en-US'."
                 },
                 "meetingType": {
                   "type": "string",
@@ -21581,93 +21587,6 @@
       "operationId": "guestMeetingAttendeeOptions"
     }
   },
-  {
-    "name": "meeting_transcription",
-    "description": "Manage Meeting Transcription",
-    "inputSchema": {
-      "type": "object",
-      "properties": {
-        "action": {
-          "type": "string",
-          "description": "Transcription action: start or stop",
-          "enum": [
-            "start",
-            "stop"
-          ]
-        },
-        "requestBody": {
-          "title": "MeetingTranscriptionRequestBody",
-          "type": "object",
-          "required": [
-            "data"
-          ],
-          "properties": {
-            "data": {
-              "title": "MeetingTranscriptionRequestBodyData",
-              "type": "object",
-              "required": [
-                "type",
-                "attributes"
-              ],
-              "properties": {
-                "type": {
-                  "type": "string",
-                  "enum": [
-                    "transcriptions"
-                  ]
-                },
-                "attributes": {
-                  "title": "MeetingTranscriptionSettingsSchema",
-                  "type": "object",
-                  "properties": {
-                    "languageCode": {
-                      "type": "string",
-                      "description": "Transcribe language code (e.g. en-US, de-DE, es-US)",
-                      "default": "en-US"
-                    },
-                    "region": {
-                      "type": "string",
-                      "description": "AWS region for Amazon Transcribe",
-                      "default": "us-east-1"
-                    },
-                    "contentIdentificationType": {
-                      "type": "string",
-                      "description": "PII content identification type",
-                      "enum": [
-                        "PII"
-                      ]
-                    }
-                  }
-                }
-              }
-            }
-          }
-        }
-      },
-      "required": [
-        "action",
-        "requestBody"
-      ]
-    },
-    "_meta": {
-      "method": "POST",
-      "path": "/v1/meetings/{meetingId}/transcription",
-      "operationId": "meetingTranscription"
-    }
-  },
-  {
-    "name": "meeting_transcription_options",
-    "description": "Meeting Transcription Options",
-    "inputSchema": {
-      "type": "object",
-      "properties": {}
-    },
-    "_meta": {
-      "method": "OPTIONS",
-      "path": "/v1/meetings/{meetingId}/transcription",
-      "operationId": "meetingTranscriptionOptions"
-    }
-  },
   {
     "name": "create_meeting_ai_session",
     "description": "Create Meeting AI Session",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@smartytalent/mcp-tools",
-  "version": "0.9.42",
+  "version": "0.9.44",
   "description": "MCP tool definitions for SmartyTalent API",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",