@agifyai/leadify-mcp 6.0.0 → 6.0.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/dataroom.js
CHANGED
|
@@ -276,16 +276,17 @@ export function registerDataRoomTools(server) {
|
|
|
276
276
|
}
|
|
277
277
|
});
|
|
278
278
|
// ── get_outreach_context ──────────────────────────────────────────────
|
|
279
|
-
server.tool("get_outreach_context", "Get a
|
|
280
|
-
"
|
|
281
|
-
"
|
|
279
|
+
server.tool("get_outreach_context", "Get a lean outreach context for a lead group. Returns the shape " +
|
|
280
|
+
"`{ leadGroupId, leadGroupName, organizationId, company }` where `company` is the " +
|
|
281
|
+
"outreach-relevant slice of companyInfo (identity, pitch, constraints, curated " +
|
|
282
|
+
"products, economics triggers/baseline, product ICP roles, proof wording). " +
|
|
282
283
|
"Takes a lead_group_id (NOT organization_id) — the org is resolved server-side, " +
|
|
283
284
|
"eliminating the cross-org footgun of get_data_room. " +
|
|
284
|
-
"
|
|
285
|
-
"
|
|
286
|
-
"
|
|
287
|
-
"
|
|
288
|
-
"
|
|
285
|
+
"Does NOT require a persona: the group needs no linked persona and an empty data " +
|
|
286
|
+
"room returns success (not an error). No persona or outreach block is returned. " +
|
|
287
|
+
"Outreach configuration (positioning, tone, rules, templates, etc.) is managed " +
|
|
288
|
+
"exclusively via the Fine Tuning tools (append_fine_tuning / set_fine_tuning / " +
|
|
289
|
+
"get_fine_tuning). " +
|
|
289
290
|
"Use this instead of get_data_room + get_lead_group_persona in the outreach " +
|
|
290
291
|
"pipeline Phase 0.", {
|
|
291
292
|
lead_group_id: z.string().describe("ID of the lead group to resolve context for."),
|
|
@@ -29,7 +29,9 @@ export function registerFineTuningTools(server) {
|
|
|
29
29
|
lead_group_id: z
|
|
30
30
|
.string()
|
|
31
31
|
.describe("ID of the lead group whose fine tuning configuration to fetch. " +
|
|
32
|
-
"
|
|
32
|
+
"Pass the lead_group_id directly; if you need to resolve it, use " +
|
|
33
|
+
"pipeline_next_lead (do NOT use get_leads — its payload is huge and is " +
|
|
34
|
+
"banned in the outreach pipeline)."),
|
|
33
35
|
}, async ({ lead_group_id }) => {
|
|
34
36
|
try {
|
|
35
37
|
const data = await getClient().get(`/api/lead-group/${encodeURIComponent(lead_group_id)}/fine-tuning`);
|
package/dist/tools/pipeline.js
CHANGED
|
@@ -21,7 +21,13 @@ export function registerPipelineTools(server) {
|
|
|
21
21
|
"`get_lead` call); the caller only needs `lead_id`. " +
|
|
22
22
|
"The response is decorated with a Trigger.dev `traceUrl` deep-link when missing " +
|
|
23
23
|
"(https://cloud.trigger.dev/runs/{runId}), so you can always jump to the trace. " +
|
|
24
|
-
"
|
|
24
|
+
"WAIT BEHAVIOR: this is a single blocking HTTP call to the backend with no " +
|
|
25
|
+
"client-side timeout — the wait is entirely server-side. The backend may return " +
|
|
26
|
+
"BEFORE the agent finishes (observed ~120s) with `status: EXECUTING` and a runId; " +
|
|
27
|
+
"this is NOT a failure — the run keeps going server-side, follow it via the " +
|
|
28
|
+
"traceUrl. In dry-run (dryrun=true) the call is safe to retry, since nothing is " +
|
|
29
|
+
"persisted; for production writes (dryrun=false) prefer following the trace over " +
|
|
30
|
+
"blindly retrying to avoid duplicate generation.", {
|
|
25
31
|
lead_id: z.string().describe("ID of the lead to generate a message for."),
|
|
26
32
|
dryrun: z
|
|
27
33
|
.boolean()
|