@agifyai/leadify-mcp 3.4.0 → 3.6.0

package/dist/server.js

@@ -16,7 +16,7 @@ import { registerPipelineTools } from "./tools/pipeline.js";
 export function createServer() {
     const server = new McpServer({
         name: "leadify",
-        version: "3.4.0",
+        version: "3.6.0",
     });
     registerAuthTools(server);
     registerOrganizationTools(server);

package/dist/tools/fine_tuning.js

@@ -4,6 +4,17 @@ 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.
+//
+// Two write tools coexist by design, with NON-OVERLAPPING contracts:
+//   - append_fine_tuning  → ALWAYS appends, never replaces. Contractual guarantee
+//                            for the iterative build-up pattern (skill operator
+//                            accumulates rules and examples as the user iterates).
+//   - set_fine_tuning     → WHOLESALE replace of ONE section. Use when you need
+//                            to wipe + rewrite a section cleanly (e.g. after a big
+//                            refactor, or to clear a section by passing empty
+//                            content).
+// The split exists so neither caller is ever confused about which behavior
+// they triggered.
 export function registerFineTuningTools(server) {
     // ── get_fine_tuning ───────────────────────────────────────────────────
     server.tool("get_fine_tuning", "Get the fine tuning configuration for a specific lead group. Returns exactly " +
@@ -30,4 +41,44 @@ export function registerFineTuningTools(server) {
             return handleToolError(error);
         }
     });
+    // ── set_fine_tuning ───────────────────────────────────────────────────
+    // WHOLESALE replace of one Fine Tuning section. Distinct from
+    // append_fine_tuning (which is append-only, contractual). Both tools
+    // coexist intentionally — pick the right one for the intent.
+    server.tool("set_fine_tuning", "WHOLESALE replace ONE section of the fine tuning configuration for a lead group. " +
+        "The target section is fully overwritten with the new content. " +
+        "This is the destructive counterpart of append_fine_tuning: use it when you need " +
+        "to wipe and rewrite a section cleanly (big refactor, schema change, full clear). " +
+        "SIBLING SECTIONS ARE NOT TOUCHED. Only the named section is replaced; the other 3 " +
+        "Markdown sections, supportedLanguages, and fallbackLanguage stay intact. " +
+        "To clear a section, pass content=\"\". " +
+        "DO NOT use this for incremental edits — use append_fine_tuning instead so the " +
+        "iterative build-up pattern is preserved (no accidental wipe of accumulated rules " +
+        "or examples). " +
+        "The 4 replaceable sections are: nonNegotiableRules, pitfalls, structure, examples. " +
+        "Languages (supportedLanguages, fallbackLanguage) are managed separately via the " +
+        "Fine Tuning UI or by a dedicated languages tool — this endpoint does not touch them.", {
+        lead_group_id: z
+            .string()
+            .describe("ID of the lead group whose fine tuning section to overwrite."),
+        section: z
+            .enum(["nonNegotiableRules", "pitfalls", "structure", "examples"])
+            .describe("Which Fine Tuning section to replace. One of: " +
+            "nonNegotiableRules | pitfalls | structure | examples."),
+        content: z
+            .string()
+            .describe("New content for the section (Markdown). The section is replaced WHOLESALE — " +
+            "any previous content is lost. Pass an empty string to clear the section."),
+    }, async ({ lead_group_id, section, content }) => {
+        try {
+            const data = await getClient().put(`/api/lead-group/${encodeURIComponent(lead_group_id)}/fine-tuning`, { section, content });
+            return toolResult({
+                ...(data && typeof data === "object" ? data : {}),
+                _note: `Wholesale replace of section '${section}' for lead group ${lead_group_id}.`,
+            });
+        }
+        catch (error) {
+            return handleToolError(error);
+        }
+    });
 }

package/dist/tools/pipeline.js

@@ -15,24 +15,14 @@ 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. " +
-        "`campaign_id` is OPTIONAL: when omitted, the MCP sends no campaign hint to the backend " +
-        "(useful for dry-runs, smoke tests, or skill flows that want to skip the pilot-pinning). " +
-        "When provided, it must be a pilot slug (e.g. 'agify-medtech-fr-v2') that matches a pilot " +
-        "file pair in the Trigger.dev repo (pilots/{campaign_id}.md + .json), paired to the lead's " +
-        "group. The writer hard-fails if the pilot is missing on a real run. " +
-        "The lead's `leadGroupId` is resolved server-side from the lead (one extra " +
+        "The pilot pinning (which Trigger.dev pilot/copywriting ruleset to follow) is resolved " +
+        "server-side from the lead's group — the caller never has to pass a campaign id. " +
+        "The lead's `leadGroupId` is also 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()
-            .optional()
-            .describe("OPTIONAL 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. " +
-            "Omit to skip the pilot-pinning (e.g. for dry-runs or smoke tests)."),
         dryrun: z
             .boolean()
             .optional()
@@ -46,7 +36,7 @@ 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, campaign_id, dryrun, force }) => {
+    }, async ({ lead_id, dryrun, force }) => {
         try {
             // Resolve leadGroupId server-side. The Trigger.dev task payload requires
             // `leadGroupId`, but the lead_id alone is enough on the MCP side — we
@@ -62,17 +52,16 @@ export function registerPipelineTools(server) {
                     `The lead was not found, or it has no groupId. ` +
                     `Check that the lead exists via get_lead.`);
             }
+            // No campaign_id is sent — pilot pinning is resolved server-side from
+            // the lead's group. Keeping the field out of the MCP surface is a
+            // SILO move: the caller (human or LLM) does not need to know about
+            // pilot slugs, and there's no risk of passing a stale or wrong slug.
             const body = {
                 leadId: lead_id,
                 leadGroupId,
                 dryrun,
                 force,
             };
-            // campaignId is optional: only include it when the caller passed one.
-            // Backend defaults are left to handle the omitted case.
-            if (campaign_id !== undefined) {
-                body.campaignId = campaign_id;
-            }
             const data = (await getClient().post("/api/trigger-outreach", body));
             // Decorate the response with a Trigger.dev run deep-link when the
             // backend didn't ship one. Applies to BOTH success and failure paths

package/package.json

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