@smartytalent/mcp-tools 0.9.11 → 0.9.12
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 +40 -2
- package/package.json +1 -1
package/dist/tools.json
CHANGED
|
@@ -17507,7 +17507,7 @@
|
|
|
17507
17507
|
},
|
|
17508
17508
|
"relationships": {
|
|
17509
17509
|
"title": "TaskRelationshipsRequestSchema",
|
|
17510
|
-
"description": "Request shape: to-one links keyed plural (jobs/conversations/emails/talents/candidates). `author` is deliberately NOT here - it is stamped server-side from the authorizer and is immutable. On PATCH each key merges independently; a {data: null} link is a no-op (unlinking is not a PATCH door). Operator lane: an emails:reply task names the thread through `conversations` (and optionally the answered mail through `emails`); an emails:compose task names the addressee through `talents` or `candidates` (a candidate resolves to its talent's e-mail) or, failing both, through meta.recipientEmail; an emails:send task names the held draft through `emails`.",
|
|
17510
|
+
"description": "Request shape: to-one links keyed plural (jobs/briefs/conversations/emails/talents/candidates). `author` is deliberately NOT here - it is stamped server-side from the authorizer and is immutable. On PATCH each key merges independently; a {data: null} link is a no-op (unlinking is not a PATCH door). Operator lane: an emails:reply task names the thread through `conversations` (and optionally the answered mail through `emails`); an emails:compose task names the addressee through `talents` or `candidates` (a candidate resolves to its talent's e-mail) or, failing both, through meta.recipientEmail; an emails:send task names the held draft through `emails`.",
|
|
17511
17511
|
"type": "object",
|
|
17512
17512
|
"properties": {
|
|
17513
17513
|
"jobs": {
|
|
@@ -17528,6 +17528,25 @@
|
|
|
17528
17528
|
}
|
|
17529
17529
|
}
|
|
17530
17530
|
},
|
|
17531
|
+
"briefs": {
|
|
17532
|
+
"title": "TaskRelationshipsRequestBriefsSchema",
|
|
17533
|
+
"description": "The brief this task concerns; the intent-inbox writers set it, and an operator task may carry it for context.",
|
|
17534
|
+
"type": "object",
|
|
17535
|
+
"properties": {
|
|
17536
|
+
"data": {
|
|
17537
|
+
"title": "TaskRelationshipsRequestBriefsDataSchema",
|
|
17538
|
+
"type": "object",
|
|
17539
|
+
"properties": {
|
|
17540
|
+
"type": {
|
|
17541
|
+
"type": "string"
|
|
17542
|
+
},
|
|
17543
|
+
"id": {
|
|
17544
|
+
"type": "string"
|
|
17545
|
+
}
|
|
17546
|
+
}
|
|
17547
|
+
}
|
|
17548
|
+
}
|
|
17549
|
+
},
|
|
17531
17550
|
"conversations": {
|
|
17532
17551
|
"title": "TaskRelationshipsRequestConversationsSchema",
|
|
17533
17552
|
"type": "object",
|
|
@@ -17733,7 +17752,7 @@
|
|
|
17733
17752
|
},
|
|
17734
17753
|
"relationships": {
|
|
17735
17754
|
"title": "TaskRelationshipsRequestSchema",
|
|
17736
|
-
"description": "Request shape: to-one links keyed plural (jobs/conversations/emails/talents/candidates). `author` is deliberately NOT here - it is stamped server-side from the authorizer and is immutable. On PATCH each key merges independently; a {data: null} link is a no-op (unlinking is not a PATCH door). Operator lane: an emails:reply task names the thread through `conversations` (and optionally the answered mail through `emails`); an emails:compose task names the addressee through `talents` or `candidates` (a candidate resolves to its talent's e-mail) or, failing both, through meta.recipientEmail; an emails:send task names the held draft through `emails`.",
|
|
17755
|
+
"description": "Request shape: to-one links keyed plural (jobs/briefs/conversations/emails/talents/candidates). `author` is deliberately NOT here - it is stamped server-side from the authorizer and is immutable. On PATCH each key merges independently; a {data: null} link is a no-op (unlinking is not a PATCH door). Operator lane: an emails:reply task names the thread through `conversations` (and optionally the answered mail through `emails`); an emails:compose task names the addressee through `talents` or `candidates` (a candidate resolves to its talent's e-mail) or, failing both, through meta.recipientEmail; an emails:send task names the held draft through `emails`.",
|
|
17737
17756
|
"type": "object",
|
|
17738
17757
|
"properties": {
|
|
17739
17758
|
"jobs": {
|
|
@@ -17754,6 +17773,25 @@
|
|
|
17754
17773
|
}
|
|
17755
17774
|
}
|
|
17756
17775
|
},
|
|
17776
|
+
"briefs": {
|
|
17777
|
+
"title": "TaskRelationshipsRequestBriefsSchema",
|
|
17778
|
+
"description": "The brief this task concerns; the intent-inbox writers set it, and an operator task may carry it for context.",
|
|
17779
|
+
"type": "object",
|
|
17780
|
+
"properties": {
|
|
17781
|
+
"data": {
|
|
17782
|
+
"title": "TaskRelationshipsRequestBriefsDataSchema",
|
|
17783
|
+
"type": "object",
|
|
17784
|
+
"properties": {
|
|
17785
|
+
"type": {
|
|
17786
|
+
"type": "string"
|
|
17787
|
+
},
|
|
17788
|
+
"id": {
|
|
17789
|
+
"type": "string"
|
|
17790
|
+
}
|
|
17791
|
+
}
|
|
17792
|
+
}
|
|
17793
|
+
}
|
|
17794
|
+
},
|
|
17757
17795
|
"conversations": {
|
|
17758
17796
|
"title": "TaskRelationshipsRequestConversationsSchema",
|
|
17759
17797
|
"type": "object",
|