@agifyai/leadify-mcp 2.0.0 → 3.2.0

package/dist/tools/dataroom.js

@@ -170,11 +170,13 @@ const ORG_ID_DESC = "REQUIRED Clerk organization ID targeting the org whose data
     "data room (read or write). Requires admin access for writes.";
 const DRY_RUN_DESC = "If true, validate the merged payload + return the preview WITHOUT writing. " +
     "Use to dry-fit a change before persisting.";
-async function fetchDataRoom(organizationId) {
-    const params = organizationId
-        ? new URLSearchParams({ organizationId })
-        : undefined;
-    const data = (await getClient().get("/api/data-room", params));
+async function fetchDataRoom(organizationId, opts) {
+    const params = new URLSearchParams();
+    if (organizationId)
+        params.set("organizationId", organizationId);
+    if (opts?.includePersonas)
+        params.set("includePersonas", "true");
+    const data = (await getClient().get("/api/data-room", params.toString() ? params : undefined));
     return data ?? {};
 }
 function currentCompanyInfo(state) {
@@ -242,13 +244,26 @@ async function mergeAndPut(organizationId, dry_run, patcher, validationHint) {
 // ─── Tool registrations ────────────────────────────────────────────────────
 export function registerDataRoomTools(server) {
     // ── get_data_room ──────────────────────────────────────────────────────
-    server.tool("get_data_room", "Retrieve the organization's full data room: company info (v2 schema), all documents, and " +
-        "every persona defined for the workspace. Use this as the entry point when you need to " +
-        "understand the company's context before writing campaigns or messages.", {
+    server.tool("get_data_room", "Retrieve the organization's data room: company info (v2 schema) and all documents. " +
+        "Use this as the entry point when you need to understand the company's context " +
+        "before writing campaigns or messages. " +
+        "By default, `personas[]` is NO LONGER included in the response (slimed down to " +
+        "keep the LLM context small — the data room itself was 158k chars). " +
+        "Pass `include_personas=true` to restore the legacy full payload (escape hatch). " +
+        "For per-persona queries, prefer the `list_personas` tool.", {
         organization_id: z.string().describe(ORG_ID_DESC),
-    }, async ({ organization_id }) => {
+        include_personas: z
+            .boolean()
+            .optional()
+            .default(false)
+            .describe("If true, include the full `personas[]` array in the response (legacy " +
+            "behaviour, ~150k chars). If false (default), personas are omitted — use " +
+            "`list_personas` for per-persona queries."),
+    }, async ({ organization_id, include_personas }) => {
         try {
-            const data = await fetchDataRoom(organization_id);
+            const data = await fetchDataRoom(organization_id, {
+                includePersonas: include_personas === true,
+            });
             return toolResult(data);
         }
         catch (error) {

package/dist/tools/fine_tuning.d.ts

@@ -0,0 +1,2 @@
+import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
+export declare function registerFineTuningTools(server: McpServer): void;

package/dist/tools/fine_tuning.js

@@ -0,0 +1,33 @@
+import { z } from "zod";
+import { getClient } from "../client.js";
+import { toolResult, handleToolError } from "../types.js";
+// Dedicated tool for the Fine Tuning page (separate from OutreachSettings).
+// Both concepts live in the DB (FineTuning + OutreachSettings) and the API
+// keeps them strictly separated: this endpoint NEVER touches OutreachSettings.
+export function registerFineTuningTools(server) {
+    // ── get_fine_tuning ───────────────────────────────────────────────────
+    server.tool("get_fine_tuning", "Get the fine tuning configuration for a specific lead group. Returns exactly " +
+        "the 5 levers of the Fine Tuning page and nothing else: " +
+        "(1) nonNegotiableRules (Markdown), (2) pitfalls (Markdown), (3) structure (Markdown), " +
+        "(4) supportedLanguages (string[]), (5) examples (Markdown), plus fallbackLanguage. " +
+        "Read STRICTLY from the FineTuning model — zero OutreachSettings mixed in. " +
+        "Use this when editing the Fine Tuning page or when an agent needs the copywriting " +
+        "guardrails (rules + pitfalls + structure + examples + languages). " +
+        "DO NOT use get_outreach_settings for this: that endpoint returns 100× more payload " +
+        "and is for the Outreach agent preflight, not for fine tuning. " +
+        "Upsert-on-read: if no FineTuning row exists for the lead group, one is created " +
+        "with defaults, so the response shape is always stable.", {
+        lead_group_id: z
+            .string()
+            .describe("ID of the lead group whose fine tuning configuration to fetch. " +
+            "Resolve via list_organizations + get_leads if needed."),
+    }, async ({ lead_group_id }) => {
+        try {
+            const data = await getClient().get(`/api/lead-group/${encodeURIComponent(lead_group_id)}/fine-tuning`);
+            return toolResult(data);
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
+}

package/dist/tools/lead_groups.js

@@ -158,11 +158,26 @@ export function registerLeadGroupTools(server) {
     // ── get_lead_group_persona ─────────────────────────────────────────────
     server.tool("get_lead_group_persona", "Retrieve the persona assigned to a specific lead group, with group context. " +
         "Returns null persona if none is assigned. Use this to check what targeting " +
-        "rules apply to a group before generating messages.", {
+        "rules apply to a group before generating messages. " +
+        "By default, `persona` is SLIM ({id, name, organizationId}) — about ~150 chars " +
+        "instead of 69k — just enough to resolve the org / link the persona to a lead group. " +
+        "Pass `view=full` to get the complete persona (legacy behaviour). " +
+        "Pass `view=outreach` to get the outreach-specific projection.", {
         lead_group_id: z.string().describe("Lead group ID."),
-    }, async ({ lead_group_id }) => {
+        view: z
+            .enum(["slim", "outreach", "full"])
+            .optional()
+            .default("slim")
+            .describe("Persona projection. " +
+            "'slim' (default) = {id, name, organizationId} — fast, context-friendly. " +
+            "'outreach' = projection used by the outreach agent (messaging + targeting). " +
+            "'full' = complete persona payload (legacy 69k-char shape, escape hatch)."),
+    }, async ({ lead_group_id, view }) => {
         try {
-            const data = await getClient().get(`/api/lead-group/${encodeURIComponent(lead_group_id)}/persona`);
+            const params = new URLSearchParams();
+            if (view)
+                params.set("view", view);
+            const data = await getClient().get(`/api/lead-group/${encodeURIComponent(lead_group_id)}/persona`, params);
             return toolResult(data);
         }
         catch (error) {

package/dist/tools/leads.js

@@ -107,7 +107,11 @@ export function registerLeadTools(server) {
         "group membership, creation/update timestamps, related leads (if relations are " +
         "configured), and the group schema. Use this when you already have a lead ID " +
         "and need its complete information. For searching or browsing multiple leads, " +
-        "use get_leads instead.", {
+        "use get_leads instead. " +
+        "Note: the group schema lives at `lead.group.schema` (no top-level `schema` " +
+        "field). System-level `select` field options (qualification_level, " +
+        "qualification_status, seniority, institution_type) are reconciled against the " +
+        "canonical registry, so all legitimate values are listed.", {
         id: z.string().describe("The unique ID of the lead to retrieve."),
     }, async ({ id }) => {
         try {

package/dist/tools/outreach_settings.js

@@ -78,11 +78,24 @@ export function registerOutreachSettingsTools(server) {
     // ── get_outreach_settings ──────────────────────────────────────────────
     server.tool("get_outreach_settings", "Get the outreach settings (positioning, sequence design, rules, URLs, case studies) " +
         "for a specific lead group / campaign. The settings drive the [Leadify] Outreach agent " +
-        "preflight. GET auto-creates a row with defaults on first read.", {
+        "preflight. GET auto-creates a row with defaults on first read. " +
+        "Pass `sections` (CSV) to slice the response and avoid saturating the LLM context " +
+        "when you only need one part (e.g. 'positioning,urls'). Allowed: " +
+        "positioning, sequenceDesign, rules, caseStudies, urls, connection.", {
         lead_group_id: z.string().describe("Lead group ID."),
-    }, async ({ lead_group_id }) => {
+        sections: z
+            .string()
+            .optional()
+            .describe("Optional CSV of section names to return. " +
+            "Allowed values: positioning, sequenceDesign, rules, caseStudies, urls, connection. " +
+            "If omitted, the full row is returned (legacy behaviour). " +
+            "Use this to keep the LLM context small when you only need one section."),
+    }, async ({ lead_group_id, sections }) => {
         try {
-            const data = await getClient().get(`/api/lead-group/${encodeURIComponent(lead_group_id)}/outreach-settings`);
+            const params = new URLSearchParams();
+            if (sections)
+                params.set("sections", sections);
+            const data = await getClient().get(`/api/lead-group/${encodeURIComponent(lead_group_id)}/outreach-settings`, params);
             return toolResult(data);
         }
         catch (error) {

package/dist/tools/pipeline.js

@@ -1,6 +1,6 @@
 import { z } from "zod";
 import { getClient } from "../client.js";
-import { toolResult, handleToolError } from "../types.js";
+import { toolResult, toolError, handleToolError } from "../types.js";
 export function registerPipelineTools(server) {
     // ── trigger_outreach ─────────────────────────────────────────────────────
     server.tool("trigger_outreach", "Generate the outreach message SEQUENCE for a lead via the Trigger.dev agent " +
@@ -15,8 +15,21 @@ export function registerPipelineTools(server) {
         "card_* sequence fields to lead.data). " +
         "The 'force' flag (default false) bypasses the 'already has a message?' guard — " +
         "useful for re-generating on an already-processed lead. " +
+        "REQUIRES a 'campaign_id': the pilot slug (e.g. 'agify-medtech-fr-v2') that selects " +
+        "which copywriting pilot the writer follows. It is NOT a DB id — it must match a pilot " +
+        "authored in the Trigger.dev repo (pilots/{campaign_id}.md + .json), and that pilot's " +
+        ".json is paired to the lead's group. The skill operator picks it; there is no default. " +
+        "The lead's `leadGroupId` is resolved server-side from the lead (one extra " +
+        "`get_lead` call); the caller only needs `lead_id`. " +
+        "The response is decorated with a Trigger.dev `traceUrl` deep-link when missing " +
+        "(https://cloud.trigger.dev/runs/{runId}), so you can always jump to the trace. " +
         "Waits up to 120s for the remote agent to complete.", {
         lead_id: z.string().describe("ID of the lead to generate a message for."),
+        campaign_id: z
+            .string()
+            .describe("Pilot slug driving the copywriting (e.g. 'agify-medtech-fr-v2'). NOT a DB campaign id. " +
+            "Must match a pilot file pair in the Trigger.dev repo whose .json is paired to this " +
+            "lead's group. The writer hard-fails if the pilot is missing."),
         dryrun: z
             .boolean()
             .optional()
@@ -30,13 +43,35 @@ export function registerPipelineTools(server) {
             .default(false)
             .describe("true = bypass the 'already has a message?' check so you can re-generate. " +
             "false (default) = normal behaviour: skip leads that already have card_message."),
-    }, async ({ lead_id, dryrun, force }) => {
+    }, async ({ lead_id, campaign_id, dryrun, force }) => {
         try {
-            const data = await getClient().post("/api/trigger-outreach", {
+            // Resolve leadGroupId server-side. The Trigger.dev task payload requires
+            // `leadGroupId`, but the lead_id alone is enough on the MCP side — we
+            // fetch the lead to extract groupId instead of forcing the caller (human
+            // or LLM) to pass it manually. One extra HTTP call, dwarfed by the
+            // 10–60s Trigger.dev wait that follows.
+            const leadParams = new URLSearchParams();
+            leadParams.set("id", lead_id);
+            const leadRes = (await getClient().get("/get-lead", leadParams));
+            const leadGroupId = leadRes?.lead?.groupId;
+            if (!leadGroupId) {
+                return toolError(`Cannot resolve leadGroupId for lead "${lead_id}". ` +
+                    `The lead was not found, or it has no groupId. ` +
+                    `Check that the lead exists via get_lead.`);
+            }
+            const data = (await getClient().post("/api/trigger-outreach", {
                 leadId: lead_id,
+                leadGroupId,
+                campaignId: campaign_id,
                 dryrun,
                 force,
-            });
+            }));
+            // Decorate the response with a Trigger.dev run deep-link when the
+            // backend didn't ship one. Applies to BOTH success and failure paths
+            // so the skill operator can always jump to the trace.
+            if (data?.runId && !data.traceUrl) {
+                data.traceUrl = `https://cloud.trigger.dev/runs/${data.runId}`;
+            }
             return toolResult(data);
         }
         catch (error) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agifyai/leadify-mcp",
-  "version": "2.0.0",
+  "version": "3.2.0",
   "description": "MCP server for Leadify lead management API",
   "type": "module",
   "main": "dist/index.js",