@apex-inc/mcp-server 0.21.0 → 0.22.1
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.d.ts +30 -10
- package/dist/tools.d.ts.map +1 -1
- package/dist/tools.js +83 -14
- package/dist/tools.js.map +1 -1
- package/package.json +1 -1
- package/skills/apex-communications/SKILL.md +18 -0
package/package.json
CHANGED
|
@@ -62,6 +62,24 @@ Read these resources before suggesting communications-related actions to underst
|
|
|
62
62
|
|
|
63
63
|
## Common Patterns
|
|
64
64
|
|
|
65
|
+
### "Which template should I attach to this journey send step / broadcast?"
|
|
66
|
+
|
|
67
|
+
`list_communications` IS the picker — use its filters instead of dumping every comm and eyeballing it:
|
|
68
|
+
|
|
69
|
+
```
|
|
70
|
+
1. list_communications(pipeline="transactional", channel="email")
|
|
71
|
+
→ narrow to the pipeline + channel the step needs. 'transactional'
|
|
72
|
+
bypasses opt-out and is ONLY valid after a recipient-initiated trigger
|
|
73
|
+
(user_signup, password_reset_requested). 'marketing' is consent-gated.
|
|
74
|
+
2. Read each row's subject + one-line body preview to disambiguate similar
|
|
75
|
+
titles — you do NOT need to preview_communication every candidate.
|
|
76
|
+
3. Pick by `id` (+ its version) and attach it to the send step.
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
Pipeline is load-bearing: attaching a `transactional` comm to a passive-trigger
|
|
80
|
+
journey (schedule / audience-entry / passive event) is a **publish-time
|
|
81
|
+
hard-block**. For those journeys, filter to `pipeline="marketing"`.
|
|
82
|
+
|
|
65
83
|
### "I need to send a welcome email"
|
|
66
84
|
```
|
|
67
85
|
1. recommend_communications → look for "welcome" in results
|