@leadbay/mcp 0.23.0 → 0.23.1

package/dist/http-server.js

@@ -6534,9 +6534,13 @@ var COMPOSITE_FILE_TOOL_NAMES = /* @__PURE__ */ new Set([
   "leadbay_campaign_call_sheet",
   "leadbay_campaign_progression",
   "leadbay_create_campaign",
+  "leadbay_create_custom_field",
+  "leadbay_delete_custom_field",
   "leadbay_enrich_titles",
   "leadbay_extend_lens",
   "leadbay_followups_map",
+  "leadbay_get_lead_custom_fields",
+  "leadbay_get_qualification_questions",
   "leadbay_import_and_qualify",
   "leadbay_import_leads",
   "leadbay_import_status",
@@ -6557,7 +6561,9 @@ var COMPOSITE_FILE_TOOL_NAMES = /* @__PURE__ */ new Set([
   "leadbay_resolve_import_rows",
   "leadbay_scan_portfolio_signals",
   "leadbay_seed_candidates",
+  "leadbay_set_qualification_questions",
   "leadbay_team_activity",
+  "leadbay_update_custom_field",
   "leadbay_tour_plan"
 ]);
 
@@ -7406,6 +7412,23 @@ WHEN TO USE: when a quota error has blocked the user's intent and they want to k
 
 WHEN NOT TO USE: pre-flight (the agent is not paying \u2014 the user is); for subscription / plan changes use \`leadbay_open_billing_portal\` instead; for read-only quota diagnostics use \`leadbay_account_status\` / \`leadbay_get_quota\`.
 `;
+var leadbay_delete_custom_field = `Delete an org-level CRM custom field. Use when the user explicitly wants to remove a custom field from their account \u2014 e.g. "delete the old 'Legacy Source' field".
+
+**This is destructive.** Removing the field drops its stored values from every lead and breaks any import mapping that targets \`CUSTOM.<id>\`. For that reason the tool has a safety gate:
+
+- Call with \`id\` only \u2192 the tool returns the field that WOULD be deleted (\`{id, name, type, deleted:false, hint}\`) and changes nothing. Surface the hint to the user and ask them to confirm.
+- Call with \`id\` + \`confirm:true\` \u2192 the field is deleted (\`{id, name, type, deleted:true}\`).
+
+\`id\` is the numeric custom-field id from \`leadbay_list_mappable_fields\` \u2014 NOT the \`CUSTOM.<id>\` mapping value.
+
+WHEN TO USE: the user explicitly asks to delete/remove a custom field \u2014 and only fire with confirm:true after they confirm.
+
+WHEN NOT TO USE: to rename or retype a field (use leadbay_update_custom_field) or to create one (use leadbay_create_custom_field).
+
+### RENDERING
+
+Before deleting (no confirm), render the \`hint\` and ask the user to confirm \u2014 do NOT auto-confirm on the user's behalf. After a confirmed delete, acknowledge in one line: **"Deleted custom field #12 'Legacy Source'."**
+`;
 var leadbay_deselect_leads = `Remove leads from the user's transient selection.
 
 WHEN TO USE: when narrowing a previously-built selection without clearing it entirely.
@@ -7809,6 +7832,68 @@ WHEN TO USE: to avoid redundant outreach and understand where this lead is in th
 
 WHEN NOT TO USE: when leadbay_research_lead_by_id has already been called \u2014 it includes recent prospecting actions in its engagement block.
 `;
+var leadbay_get_lead_custom_fields = `## WHEN TO USE
+
+Trigger phrases: "what custom fields are on this lead", "show the CRM custom field values for <Company>", "what's the <custom field name> on this lead", "get lead <UUID>'s custom fields", "does this lead have any custom field values".
+
+**Memory:** recall + capture via \`leadbay_agent_memory_*\` tools.
+
+Do NOT use for: "what custom fields exist on my account" \u2192 \`leadbay_list_mappable_fields\`; "give me the full research dossier on this lead" \u2192 \`leadbay_research_lead_by_id\`.
+
+Prefer when: user wants the custom-field VALUES on ONE lead; pass \`leadId\`
+
+Examples that SHOULD invoke this tool:
+- "What custom field values are stored on this lead?"
+- "Show me the CRM custom fields for that company."
+
+Examples that should NOT invoke this tool (sound similar, route elsewhere):
+- "What custom fields are defined on my account?"
+- "Give me the full research breakdown on Acme Corp."
+
+## RENDER (quick)
+
+3-column markdown table: Field | Type | Value, one row per entry. When
+\`custom_fields\` is empty, render the \`hint\` sentence instead of an empty
+table.
+
+---
+
+Retrieve the CRM custom-field **values** stored on a single lead \u2014 the actual
+data (\`value\`) per custom field, not the field definitions.
+
+This is distinct from **leadbay_list_mappable_fields**, which returns the org's
+custom-field *catalog* (the definitions: id/name/type, used for import
+mapping). This tool answers "what does *this* lead hold for each custom field".
+
+Params: \`leadId\` (required UUID); \`lensId\` (optional escape hatch \u2014 normally
+omit; auto-resolves to the active lens).
+
+Returns:
+
+- **\`custom_fields\`** \u2014 one row per value: \`{id, name, type, value}\`. The lead
+  payload embeds each field's definition, so rows are fully named without a
+  separate catalog lookup. Empty array when the org has no custom fields or
+  none are set on this lead.
+- **\`count\`** \u2014 number of values.
+- **\`hint\`** \u2014 empty-state guidance (points at \`leadbay_list_mappable_fields\`
+  and the import path), or a degradation note in the rare case a value arrived
+  without an embedded definition and the catalog fallback failed.
+
+Reading a lead marks it seen (LEAD_SEEN) the same way the research tools do, so
+it ages out of the 'new' Discover view.
+
+Companion tools: **leadbay_list_mappable_fields** for the catalog/definitions;
+**leadbay_research_lead_by_id** for the full lead dossier (signals, contacts,
+qualification answers).
+
+### RENDERING
+
+Render \`custom_fields\` as a 3-column markdown table: **Field** (\`name\`, or the
+\`id\` when name is null) \xB7 **Type** (\`type\`) \xB7 **Value** (\`value\`, or "\u2014" when
+null/empty). One row per entry, in the order returned. When \`custom_fields\` is
+empty, render the \`hint\` sentence instead of an empty table. Don't fabricate
+fields or values \u2014 render verbatim.
+`;
 var leadbay_get_lead_notes = `Read existing notes on a lead \u2014 context the human team or prior agent runs have already captured.
 
 WHEN TO USE: before adding a note via leadbay_report_outreach, to avoid duplicating or overwriting context the SDR already wrote.
@@ -7839,6 +7924,70 @@ WHEN TO USE: before contacting the lead, to avoid duplicating outreach the team
 
 WHEN NOT TO USE: when the lead summary's \`prospecting_actions_count\` is 0.
 `;
+var leadbay_get_qualification_questions = `## WHEN TO USE
+
+Trigger phrases: "what are my qualification questions", "what questions does Leadbay ask about each lead", "show me the org qualification questions", "how are my leads being qualified", "what's the qualification criteria".
+
+**Memory:** recall + capture via \`leadbay_agent_memory_*\` tools.
+
+Do NOT use for: "how did this lead score on the qualification questions" \u2192 \`leadbay_research_lead_by_id\`; "show my ideal buyer profile and intent tags" \u2192 \`leadbay_get_taste_profile\`.
+
+Prefer when: user wants the ORG-level qualification questions catalog, no lead and no buyer profile
+
+Examples that SHOULD invoke this tool:
+- "What qualification questions does Leadbay use to score my leads?"
+- "Show me my org's qualification questions."
+
+Examples that should NOT invoke this tool (sound similar, route elsewhere):
+- "How did Acme Corp answer the qualification questions?"
+- "What's my ideal buyer profile?"
+
+## RENDER (quick)
+
+Numbered list of the questions (chat-native markdown), each one line. When
+\`is_admin\` is true, append the \`hint\` as a footnote (points at
+leadbay_set_qualification_questions for editing). When the list is empty,
+render the \`hint\` instead.
+
+---
+
+Retrieve the organization's **qualification questions** \u2014 the AI-agent questions
+Leadbay scores every lead against. These are the org-level questions that drive
+each lead's qualification boost; the per-lead ANSWERS to them surface inside
+\`leadbay_research_lead_by_id\`.
+
+Returns:
+
+- **\`qualification_questions\`** \u2014 the catalog. Each: \`{question, created_at,
+  lang}\`. Ordered as the backend returns them.
+- **\`count\`** \u2014 number of configured questions.
+- **\`is_admin\`** \u2014 whether the current user is an org admin. Modifying the
+  questions (\`leadbay_set_qualification_questions\`) is an org-admin action; for
+  admins a \`hint\` points there.
+- **\`hint\`** \u2014 operator note: the modify pointer, or an empty-state message
+  when no questions are configured.
+
+This tool only READS. To change the questions, use
+**leadbay_set_qualification_questions** (add / remove / replace). The result is
+cached on the client (it reuses the same taste-profile fetch as
+\`leadbay_get_taste_profile\`), so repeated calls in a session are cheap.
+
+Companion tools: **leadbay_set_qualification_questions** to modify the questions;
+**leadbay_get_taste_profile** when the user also wants the Ideal Buyer Profile +
+purchase-intent tags; **leadbay_research_lead_by_id** for how a SPECIFIC lead
+answered these questions; **leadbay_refine_prompt** to shape the AI agent's
+behaviour.
+
+### RENDERING
+
+Render \`qualification_questions\` as a numbered list \u2014 one question per line, in
+the order returned. Lead with a short heading like **"Qualification questions
+(N)"**. When \`qualification_questions\` is empty, render the \`hint\` sentence
+instead of an empty list. When \`is_admin\` is true and there are questions,
+append the \`hint\` as a one-line footnote (points at
+leadbay_set_qualification_questions). Do not invent questions or reword them \u2014
+render verbatim.
+`;
 var leadbay_get_quota = `Read remaining quota / spend across daily, weekly, and monthly windows for the org's resources (\`llm_completion\`, \`ai_rescore\`, \`web_fetch\`). Each entry shows \`current_units\` vs \`max_units\` and \`resets_at\`.
 
 WHEN TO USE: after a 429 error, to explain to the user which window was hit and when it resets.
@@ -10001,6 +10150,28 @@ WHEN NOT TO USE: the user is just skipping ONE outreach attempt \u2014 that's a
 
 This tool MUTATES state. The caller (agent or human-in-the-loop) is responsible for confirming intent before invocation; the MCP server does not soft-prompt for confirmation. See \`annotations.destructiveHint\`.
 `;
+var leadbay_set_qualification_questions = `Modify the organization's **qualification questions** \u2014 the AI-agent questions Leadbay scores every lead against. Use when the user wants to add, remove, or rewrite their qualification questions \u2014 e.g. "add a question about whether they run install crews", "remove the flooring question", "replace my questions with these three".
+
+The backend stores the list as a whole, so this tool reads the current questions and applies your change:
+
+- **\`add\`** \u2014 append questions (deduped against the current list).
+- **\`remove\`** \u2014 drop the exact question strings you pass.
+- **\`questions\`** \u2014 replace the ENTIRE list (mutually exclusive with add/remove).
+
+Leadbay allows **at most 5** qualification questions. If a change would exceed 5, the tool rejects with a clear limit message \u2014 remove some before adding.
+
+**Dropping any existing question is destructive** \u2014 it changes how every lead is scored. Any change that removes a current question requires \`confirm:true\` \u2014 including a same-count **swap** (remove one + add one) or a \`questions\` replacement that omits a current question, not only when the list gets shorter. Without \`confirm\`, the tool previews what would be removed and applies nothing. Pure additions never need confirm.
+
+Returns the resulting \`{qualification_questions, count, previous_count, changed}\`. Phrase questions as the yes/no scoring prompts Leadbay uses (e.g. "Is the company likely to \u2026?").
+
+WHEN TO USE: the user wants to change the org's qualification questions.
+
+WHEN NOT TO USE: to READ the questions (use leadbay_get_qualification_questions) or to change a single lead's data. This is org-level \u2014 it affects scoring for ALL leads.
+
+### RENDERING
+
+After a change, confirm in one line \u2014 e.g. **"Added 1 question \u2014 you now score leads against 4 questions."** or **"Removed 'the flooring question' \u2014 3 questions remain."** Then list the resulting questions as a numbered list. When the result is a non-changing preview (a removal awaiting confirmation), surface the \`hint\` (what would be removed) and ask the user to confirm \u2014 do NOT auto-confirm.
+`;
 var leadbay_set_user_prompt = `Set the org's intelligence-refinement prompt \u2014 free-text instruction that steers Leadbay's lead recommendations beyond firmographics. Admin-only. Setting this clears any pending clarification and triggers a full intelligence regeneration (web search + high-reasoning). \`dry_run:true\` returns the call shape without contacting the backend.
 
 WHEN TO USE: low-level.
@@ -10227,6 +10398,20 @@ Returns \`{ updated: true, contact_id, contact: { id, first_name, last_name, job
 
 Requires: LEADBAY_MCP_WRITE=1 (MCP) or exposeWrite=true (OpenClaw).
 `;
+var leadbay_update_custom_field = `Update an org-level CRM custom field in place. Use when the user wants to rename a custom field or change its type/config \u2014 e.g. "rename the 'Tier' field to 'Account Tier'" or "make the ARR field a PRICE in USD".
+
+Pass \`id\` (the numeric custom-field id from \`leadbay_list_mappable_fields\` \u2014 NOT the \`CUSTOM.<id>\` mapping value) plus any of \`name\`, \`type\`, \`config\`. The update is a partial merge over the current definition: a rename-only call keeps the existing type; a retype-only call keeps the name. At least one of \`name\` / \`type\` / \`config\` is required.
+
+Type + config rules mirror creation: \`EXTERNAL_ID\` requires \`config.url_template\` containing \`{value}\`; \`PRICE\` requires \`config.currency\`; \`DATE\`/\`DATETIME\` may set \`config.format\`. Returns the updated \`{id, name, type, config, mapping_value}\`.
+
+WHEN TO USE: the user wants to change an existing custom field's name or type.
+
+WHEN NOT TO USE: to CREATE a new field (use leadbay_create_custom_field) or to DELETE one (use leadbay_delete_custom_field). To read a lead's custom-field values use leadbay_get_lead_custom_fields; to list the catalog use leadbay_list_mappable_fields.
+
+### RENDERING
+
+Confirm the change in one line naming the field and what changed, e.g. **"Renamed custom field #12 \u2192 'Account Tier' (TEXT)."** or **"Updated #13 'ARR' \u2192 PRICE (USD)."** Don't dump the raw payload.
+`;
 var leadbay_update_lens = `Update lens metadata (name, description, mode flags). Does NOT change the audience filter \u2014 use leadbay_update_lens_filter for that.
 
 WHEN TO USE: rename a lens or toggle \`multi_product_mode\` / \`use_hq_only\`.
@@ -14132,7 +14317,39 @@ var launchBulkEnrichment = {
   }
 };
 
-// ../core/dist/tools/create-custom-field.js
+// ../core/dist/composite/_custom-field-config.js
+function sanitizeConfigForType(type, rawConfig) {
+  if (!rawConfig)
+    return null;
+  let config;
+  if (typeof rawConfig === "string") {
+    try {
+      const parsed = JSON.parse(rawConfig);
+      if (!parsed || typeof parsed !== "object")
+        return null;
+      config = parsed;
+    } catch {
+      return null;
+    }
+  } else {
+    config = rawConfig;
+  }
+  switch (type) {
+    case "PRICE":
+      return config.currency != null ? { currency: config.currency } : null;
+    case "DATE":
+    case "DATETIME":
+      return "format" in config ? { format: config.format ?? null } : null;
+    case "EXTERNAL_ID": {
+      const url = config.url_template ?? config.urlTemplate;
+      return url != null ? { url_template: url } : null;
+    }
+    default:
+      return null;
+  }
+}
+
+// ../core/dist/composite/create-custom-field.js
 var createCustomField = {
   name: "leadbay_create_custom_field",
   annotations: {
@@ -14157,8 +14374,8 @@ var createCustomField = {
         description: "Custom field type: TEXT, NUMBER, PRICE, DATE, DATETIME, or EXTERNAL_ID. Defaults to TEXT."
       },
       config: {
-        type: ["object", "null"],
-        description: "Type-specific config. EXTERNAL_ID requires {url_template:'https://.../{value}'}; PRICE requires {currency:'USD'}; DATE/DATETIME may set {format}."
+        type: ["object", "string", "null"],
+        description: "Type-specific config, as an object (preferred) or a JSON string. EXTERNAL_ID requires {url_template:'https://.../{value}'}; PRICE requires {currency:'USD'}; DATE/DATETIME may set {format}."
       },
       if_not_exists: {
         type: "boolean",
@@ -14192,9 +14409,9 @@ var createCustomField = {
       throw client.makeError("CUSTOM_FIELD_NAME_REQUIRED", "name must be a non-empty string", "Pass a user-visible custom field name, e.g. 'HubSpot Contact'.", "POST /crm/custom_fields");
     }
     const type = params.type ?? "TEXT";
-    const config = params.config ?? null;
+    const config = sanitizeConfigForType(type, params.config ?? null);
     if (type === "EXTERNAL_ID") {
-      const urlTemplate = config?.url_template ?? config?.urlTemplate;
+      const urlTemplate = config?.url_template;
       if (!urlTemplate || !urlTemplate.includes("{value}")) {
         throw client.makeError("CUSTOM_FIELD_EXTERNAL_ID_TEMPLATE_REQUIRED", "EXTERNAL_ID custom fields require config.url_template containing {value}", "Use a URL template like https://app.hubspot.com/contacts/<portal-id>/record/0-1/{value}.", "POST /crm/custom_fields");
       }
@@ -14224,6 +14441,170 @@ var createCustomField = {
   }
 };
 
+// ../core/dist/composite/update-custom-field.js
+var updateCustomField = {
+  name: "leadbay_update_custom_field",
+  annotations: {
+    title: "Update CRM custom field",
+    readOnlyHint: false,
+    destructiveHint: false,
+    idempotentHint: true,
+    openWorldHint: true
+  },
+  description: leadbay_update_custom_field,
+  write: true,
+  inputSchema: {
+    type: "object",
+    properties: {
+      id: {
+        type: "string",
+        description: "Custom field id to update (the numeric id from leadbay_list_mappable_fields, NOT the 'CUSTOM.<id>' mapping value)."
+      },
+      name: {
+        type: "string",
+        description: "New user-visible name. Omit to keep the current name."
+      },
+      type: {
+        type: "string",
+        description: "New type: TEXT, NUMBER, PRICE, DATE, DATETIME, or EXTERNAL_ID. Omit to keep the current type."
+      },
+      config: {
+        type: ["object", "string", "null"],
+        description: "New type-specific config, as an object (preferred) or a JSON string. EXTERNAL_ID requires {url_template:'https://.../{value}'}; PRICE requires {currency:'USD'}; DATE/DATETIME may set {format}. Omit to keep current config."
+      }
+    },
+    required: ["id"],
+    additionalProperties: false
+  },
+  outputSchema: {
+    type: "object",
+    properties: {
+      id: { type: "string" },
+      name: { type: "string" },
+      type: { type: "string" },
+      config: { type: ["object", "null"] },
+      mapping_value: {
+        type: "string",
+        description: "Wire mapping value for import mappings, e.g. CUSTOM.123."
+      }
+    },
+    required: ["id", "name", "type", "mapping_value"]
+  },
+  execute: async (client, params) => {
+    const id = String(params.id ?? "").trim();
+    if (!id) {
+      throw client.makeError("CUSTOM_FIELD_ID_REQUIRED", "id must be a non-empty string", "Pass the custom field id from leadbay_list_mappable_fields (the numeric id, not 'CUSTOM.<id>').", "POST /crm/custom_fields/{id}");
+    }
+    if (params.name === void 0 && params.type === void 0 && params.config === void 0) {
+      throw client.makeError("CUSTOM_FIELD_NO_CHANGE", "no field to update \u2014 pass at least one of name, type, config", "Provide a new name and/or type (and config when the type needs it).", "POST /crm/custom_fields/{id}");
+    }
+    const catalog = await client.request("GET", "/crm/custom_fields");
+    const current = (catalog ?? []).find((f) => String(f.id) === id);
+    if (!current) {
+      throw client.makeError("CUSTOM_FIELD_NOT_FOUND", `no custom field with id ${id} on this org`, "Call leadbay_list_mappable_fields to see the available custom fields and their ids.", "POST /crm/custom_fields/{id}");
+    }
+    const name = params.name !== void 0 ? params.name.trim() : current.name;
+    if (!name) {
+      throw client.makeError("CUSTOM_FIELD_NAME_REQUIRED", "name must be a non-empty string", "Pass a user-visible custom field name, or omit name to keep the current one.", "POST /crm/custom_fields/{id}");
+    }
+    const type = params.type !== void 0 ? params.type : current.type;
+    const rawConfig = params.config !== void 0 ? params.config : current.config ?? null;
+    const config = sanitizeConfigForType(type, rawConfig);
+    if (type === "EXTERNAL_ID") {
+      const urlTemplate = config?.url_template;
+      if (!urlTemplate || !urlTemplate.includes("{value}")) {
+        throw client.makeError("CUSTOM_FIELD_EXTERNAL_ID_TEMPLATE_REQUIRED", "EXTERNAL_ID custom fields require config.url_template containing {value}", "Use a URL template like https://app.hubspot.com/contacts/<portal-id>/record/0-1/{value}.", "POST /crm/custom_fields/{id}");
+      }
+    }
+    const body = {
+      name,
+      type,
+      ...config ? { config } : {}
+    };
+    await client.requestVoid("POST", `/crm/custom_fields/${id}`, body);
+    return {
+      id,
+      name,
+      type,
+      config: config ?? null,
+      mapping_value: `CUSTOM.${id}`
+    };
+  }
+};
+
+// ../core/dist/composite/delete-custom-field.js
+var deleteCustomField = {
+  name: "leadbay_delete_custom_field",
+  annotations: {
+    title: "Delete CRM custom field",
+    readOnlyHint: false,
+    destructiveHint: true,
+    idempotentHint: false,
+    openWorldHint: true
+  },
+  description: leadbay_delete_custom_field,
+  write: true,
+  inputSchema: {
+    type: "object",
+    properties: {
+      id: {
+        type: "string",
+        description: "Custom field id to delete (the numeric id from leadbay_list_mappable_fields, NOT the 'CUSTOM.<id>' mapping value)."
+      },
+      confirm: {
+        type: "boolean",
+        description: "Must be true to actually delete. Without it the tool returns the field that WOULD be deleted and does nothing \u2014 a safety gate, because deletion drops the field's values from every lead."
+      }
+    },
+    required: ["id"],
+    additionalProperties: false
+  },
+  outputSchema: {
+    type: "object",
+    properties: {
+      id: { type: "string" },
+      name: { type: "string" },
+      type: { type: "string" },
+      deleted: {
+        type: "boolean",
+        description: "True when the field was deleted; false when confirm was not set."
+      },
+      hint: {
+        type: "string",
+        description: "Guidance \u2014 present when confirm was missing (re-call with confirm:true)."
+      }
+    },
+    required: ["id", "deleted"]
+  },
+  execute: async (client, params) => {
+    const id = String(params.id ?? "").trim();
+    if (!id) {
+      throw client.makeError("CUSTOM_FIELD_ID_REQUIRED", "id must be a non-empty string", "Pass the custom field id from leadbay_list_mappable_fields (the numeric id, not 'CUSTOM.<id>').", "DELETE /crm/custom_fields/{id}");
+    }
+    const catalog = await client.request("GET", "/crm/custom_fields");
+    const current = (catalog ?? []).find((f) => String(f.id) === id);
+    if (!current) {
+      throw client.makeError("CUSTOM_FIELD_NOT_FOUND", `no custom field with id ${id} on this org`, "Call leadbay_list_mappable_fields to see the available custom fields and their ids.", "DELETE /crm/custom_fields/{id}");
+    }
+    if (params.confirm !== true) {
+      return {
+        id,
+        name: current.name,
+        type: current.type,
+        deleted: false,
+        hint: `Deleting "${current.name}" removes its values from every lead and breaks any import mapping using CUSTOM.${id}. Re-call with confirm:true to proceed.`
+      };
+    }
+    await client.requestVoid("DELETE", `/crm/custom_fields/${id}`);
+    return {
+      id,
+      name: current.name,
+      type: current.type,
+      deleted: true
+    };
+  }
+};
+
 // ../core/dist/tools/like-lead.js
 var likeLead = {
   name: "leadbay_like_lead",
@@ -16588,6 +16969,302 @@ var researchLeadByNameFuzzy = {
   }
 };
 
+// ../core/dist/composite/get-qualification-questions.js
+var getQualificationQuestions = {
+  name: "leadbay_get_qualification_questions",
+  annotations: {
+    title: "Read the org's qualification questions",
+    readOnlyHint: true,
+    destructiveHint: false,
+    idempotentHint: true,
+    openWorldHint: true
+  },
+  description: leadbay_get_qualification_questions,
+  inputSchema: {
+    type: "object",
+    properties: {},
+    additionalProperties: false
+  },
+  outputSchema: {
+    type: "object",
+    properties: {
+      qualification_questions: {
+        type: "array",
+        description: "Org-level questions Leadbay scores every lead against. Each: {question, created_at, lang}.",
+        items: { type: "object" }
+      },
+      count: {
+        type: "number",
+        description: "Number of qualification questions configured."
+      },
+      is_admin: {
+        type: "boolean",
+        description: "Whether the current bearer-token holder is an org admin. Admins can modify the questions via leadbay_set_qualification_questions."
+      },
+      region: { type: "string" },
+      hint: {
+        type: "string",
+        description: "Operator note \u2014 admin edit pointer, or the empty-state message when no questions are configured."
+      },
+      _meta: { type: "object" }
+    },
+    required: ["qualification_questions"]
+  },
+  execute: async (client, _params, ctx) => {
+    const me = await client.resolveMe().catch(() => null);
+    const isAdmin = me?.admin ?? false;
+    const orgId = me?.organization?.id ?? await client.resolveOrgId();
+    const questions = await client.request("GET", `/organizations/${orgId}/ai_agent_questions`) ?? [];
+    let hint;
+    if (questions.length === 0) {
+      hint = "No qualification questions configured yet. Use leadbay_set_qualification_questions to add some, or leadbay_refine_prompt to shape the AI agent.";
+    } else if (isAdmin) {
+      hint = "You're an org admin \u2014 use leadbay_set_qualification_questions to add, remove, or replace these questions.";
+    }
+    return withAgentMemoryMeta(client, {
+      qualification_questions: questions.map((q) => ({
+        question: q.question,
+        created_at: q.created_at,
+        lang: q.lang
+      })),
+      count: questions.length,
+      is_admin: isAdmin,
+      region: client.region,
+      ...hint ? { hint } : {}
+    }, ctx);
+  }
+};
+
+// ../core/dist/composite/set-qualification-questions.js
+var setQualificationQuestions = {
+  name: "leadbay_set_qualification_questions",
+  annotations: {
+    title: "Modify the org's qualification questions",
+    readOnlyHint: false,
+    destructiveHint: true,
+    idempotentHint: false,
+    openWorldHint: true
+  },
+  description: leadbay_set_qualification_questions,
+  write: true,
+  inputSchema: {
+    type: "object",
+    properties: {
+      questions: {
+        type: "array",
+        items: { type: "string" },
+        description: "Full replacement list of qualification questions (replaces ALL current questions). Mutually exclusive with add/remove."
+      },
+      add: {
+        type: "array",
+        items: { type: "string" },
+        description: "Questions to append to the current list (deduped). Mutually exclusive with `questions`."
+      },
+      remove: {
+        type: "array",
+        items: { type: "string" },
+        description: "Exact question strings to remove from the current list. Mutually exclusive with `questions`. A removal requires confirm:true."
+      },
+      confirm: {
+        type: "boolean",
+        description: "Required whenever the change DROPS ANY existing question \u2014 including a same-count swap or a `questions` replacement that omits a current question, not only when the list gets shorter (removing a question changes how every lead is scored). Without it, such a change is previewed and not applied. Pure additions never need confirm."
+      }
+    },
+    additionalProperties: false
+  },
+  outputSchema: {
+    type: "object",
+    properties: {
+      qualification_questions: {
+        type: "array",
+        description: "The questions AFTER the change. Each: {question}.",
+        items: { type: "object" }
+      },
+      count: { type: "number" },
+      previous_count: { type: "number" },
+      changed: {
+        type: "boolean",
+        description: "True when the list was actually written; false on a no-op or an unconfirmed shrink."
+      },
+      region: { type: "string" },
+      hint: {
+        type: "string",
+        description: "Operator note \u2014 confirm prompt on a shrink, or a no-op explanation."
+      },
+      _meta: { type: "object" }
+    },
+    required: ["qualification_questions", "count", "changed"]
+  },
+  execute: async (client, params, ctx) => {
+    const hasSet = Array.isArray(params.questions);
+    const hasAdd = Array.isArray(params.add) && params.add.length > 0;
+    const hasRemove = Array.isArray(params.remove) && params.remove.length > 0;
+    if (hasSet && (hasAdd || hasRemove)) {
+      throw client.makeError("QUALIFICATION_QUESTIONS_BAD_ARGS", "`questions` (full replace) is mutually exclusive with add/remove", "Pass EITHER `questions` (the full new list) OR `add`/`remove`, not both.", "POST /organizations/{orgId}");
+    }
+    if (!hasSet && !hasAdd && !hasRemove) {
+      throw client.makeError("QUALIFICATION_QUESTIONS_NO_CHANGE", "nothing to change \u2014 pass `questions`, `add`, or `remove`", "Provide a full `questions` list, or `add`/`remove` entries.", "POST /organizations/{orgId}");
+    }
+    const orgId = await client.resolveOrgId();
+    const current = await client.request("GET", `/organizations/${orgId}/ai_agent_questions`);
+    const currentQs = (current ?? []).map((q) => q.question);
+    const norm = (s) => s.trim();
+    let next;
+    if (hasSet) {
+      next = params.questions.map(norm).filter((s) => s.length > 0);
+    } else {
+      next = [...currentQs];
+      if (hasRemove) {
+        const drop = new Set(params.remove.map(norm));
+        next = next.filter((q) => !drop.has(norm(q)));
+      }
+      if (hasAdd) {
+        const seen2 = new Set(next.map(norm));
+        for (const q of params.add.map(norm)) {
+          if (q.length > 0 && !seen2.has(q)) {
+            next.push(q);
+            seen2.add(q);
+          }
+        }
+      }
+    }
+    const seen = /* @__PURE__ */ new Set();
+    next = next.filter((q) => {
+      const k = norm(q);
+      if (seen.has(k))
+        return false;
+      seen.add(k);
+      return true;
+    });
+    const MAX_QUESTIONS = 5;
+    if (next.length > MAX_QUESTIONS) {
+      throw client.makeError("QUALIFICATION_QUESTIONS_LIMIT", `too many questions: ${next.length} (max ${MAX_QUESTIONS})`, `Leadbay allows at most ${MAX_QUESTIONS} qualification questions. Remove some first (pass fewer in \`questions\`, or use \`remove\`), then add.`, "POST /organizations/{orgId}");
+    }
+    const previousCount = currentQs.length;
+    const noChange = next.length === currentQs.length && next.every((q, i) => norm(q) === norm(currentQs[i] ?? ""));
+    if (noChange) {
+      return withAgentMemoryMeta(client, {
+        qualification_questions: currentQs.map((q) => ({ question: q })),
+        count: currentQs.length,
+        previous_count: previousCount,
+        changed: false,
+        region: client.region,
+        hint: "No change \u2014 the resulting list is identical to the current one. Pass different `add`/`remove` entries, or call leadbay_get_qualification_questions to review the current questions."
+      }, ctx);
+    }
+    const removed = currentQs.filter((q) => !next.some((n) => norm(n) === norm(q)));
+    if (removed.length > 0 && params.confirm !== true) {
+      return withAgentMemoryMeta(client, {
+        qualification_questions: currentQs.map((q) => ({ question: q })),
+        count: currentQs.length,
+        previous_count: previousCount,
+        changed: false,
+        region: client.region,
+        hint: `Re-call with confirm:true to apply. This would remove ${removed.length} question(s): ${removed.map((q) => `"${q}"`).join(", ")}. Removing a question changes how every lead is scored.`
+      }, ctx);
+    }
+    await client.requestVoid("POST", `/organizations/${orgId}`, {
+      ai_agent_lead_questions: next
+    });
+    client.invalidateTasteProfile();
+    return withAgentMemoryMeta(client, {
+      qualification_questions: next.map((q) => ({ question: q })),
+      count: next.length,
+      previous_count: previousCount,
+      changed: true,
+      region: client.region
+    }, ctx);
+  }
+};
+
+// ../core/dist/composite/get-lead-custom-fields.js
+var getLeadCustomFields = {
+  name: "leadbay_get_lead_custom_fields",
+  annotations: {
+    title: "Read a lead's custom-field values",
+    readOnlyHint: true,
+    destructiveHint: false,
+    idempotentHint: true,
+    openWorldHint: true
+  },
+  description: leadbay_get_lead_custom_fields,
+  inputSchema: {
+    type: "object",
+    properties: {
+      leadId: { type: "string", description: "Lead UUID (required)" },
+      lensId: {
+        type: "number",
+        description: "Lens id (escape hatch \u2014 normally omit; auto-resolves to the active lens)"
+      }
+    },
+    required: ["leadId"],
+    additionalProperties: false
+  },
+  outputSchema: {
+    type: "object",
+    properties: {
+      lead_id: { type: "string" },
+      custom_fields: {
+        type: "array",
+        description: "Custom-field VALUES on this lead. Each: {id, name, type, value}. Empty when the org has no custom fields or none are set on this lead.",
+        items: { type: "object" }
+      },
+      count: { type: "number" },
+      region: { type: "string" },
+      hint: {
+        type: "string",
+        description: "Operator note \u2014 empty-state guidance, or a degradation note when the lead fetch returned entries without embedded definitions."
+      },
+      _meta: { type: "object" }
+    },
+    required: ["custom_fields", "lead_id"]
+  },
+  execute: async (client, params, ctx) => {
+    const lensId = params.lensId ?? await client.resolveDefaultLens();
+    void client.request("POST", "/interactions", [
+      { type: "LEAD_SEEN", leadId: params.leadId, lensId: String(lensId) },
+      { type: "LEAD_CLICKED", leadId: params.leadId, lensId: String(lensId) }
+    ]).catch(() => {
+    });
+    const lead = await client.request("GET", `/lenses/${lensId}/leads/${params.leadId}`);
+    const entries = lead.custom_fields ?? [];
+    const needsCatalog = entries.some((e) => !e?.field?.name);
+    let catalog = null;
+    if (needsCatalog) {
+      try {
+        catalog = await client.request("GET", "/crm/custom_fields");
+      } catch (err) {
+        ctx?.logger?.warn?.(`get_lead_custom_fields: catalog fallback failed: ${err?.message ?? err?.code ?? err}`);
+      }
+    }
+    const byId = new Map((catalog ?? []).map((f) => [f.id, f]));
+    const rows = entries.map((e) => {
+      const bareId = e.id;
+      const id = e.field?.id ?? bareId ?? "";
+      const def = e.field ? void 0 : byId.get(String(id));
+      return {
+        id: String(id),
+        name: e.field?.name ?? def?.name ?? null,
+        type: e.field?.type ?? def?.type ?? null,
+        value: e.value ?? null
+      };
+    });
+    let hint;
+    if (rows.length === 0) {
+      hint = "This lead has no custom-field values. The org may have no custom fields defined \u2014 see leadbay_list_mappable_fields for the catalog, or set values via import (map a column to CUSTOM.<id>).";
+    } else if (needsCatalog && rows.some((r) => r.name === null)) {
+      hint = "Some custom fields could not be named (the lead payload omitted definitions and the catalog fetch failed). Retry, or check leadbay_list_mappable_fields.";
+    }
+    return withAgentMemoryMeta(client, {
+      lead_id: params.leadId,
+      custom_fields: rows,
+      count: rows.length,
+      region: client.region,
+      ...hint ? { hint } : {}
+    }, ctx);
+  }
+};
+
 // ../core/dist/composite/account-history.js
 var accountHistory = {
   name: "leadbay_account_history",
@@ -21538,6 +22215,15 @@ var compositeReadTools = [
   campaignCallSheet,
   researchLeadById,
   researchLeadByNameFuzzy,
+  // Org qualification questions — the AI-agent questions every lead is scored
+  // against. ALWAYS exposed (default surface): "how are my leads qualified"
+  // is a first-session question, and the underlying get_taste_profile is
+  // ADVANCED-gated. Read-only; no MCP edit endpoint exists (issue #3768).
+  getQualificationQuestions,
+  // Per-lead custom-field VALUES. ALWAYS exposed: complements the always-on
+  // list_mappable_fields (which returns DEFINITIONS only). The lead payload
+  // embeds each field's definition, so no catalog join is needed (issue #3768).
+  getLeadCustomFields,
   // accountHistory layers FULL notes + activity timeline on top of research
   // so the agent can write the US4 "why has this dormant account resurfaced"
   // narrative in ONE call. ALWAYS exposed (compositeReadTools) — the underlying
@@ -21631,6 +22317,15 @@ var compositeWriteTools = [
   // createCustomField is granular-shaped but file-import prompts depend on it
   // to preserve source-system links without requiring advanced-tool exposure.
   createCustomField,
+  // update/delete custom field — same default-surface rationale as create.
+  // delete is destructive (requires confirm:true). Both gated behind
+  // LEADBAY_MCP_WRITE=1 in MCP.
+  updateCustomField,
+  deleteCustomField,
+  // Modify the org's qualification questions (AI-agent questions). Full-replace
+  // endpoint (POST /organizations/{orgId} {ai_agent_lead_questions:[...]}); the
+  // tool reads current + applies add/remove/set. Shrinking requires confirm.
+  setQualificationQuestions,
   // addNote is granular-shaped but file-import prompts depend on it to preserve
   // meaningful source-file notes after imports return lead ids.
   addNote,
@@ -23055,7 +23750,7 @@ function parseWriteEnv(env = process.env) {
 }
 
 // src/http-server.ts
-var VERSION = true ? "0.23.0" : "0.0.0-dev";
+var VERSION = true ? "0.23.1" : "0.0.0-dev";
 var PORT = Number(process.env.PORT ?? 8080);
 var HOST = process.env.HOST ?? "0.0.0.0";
 var sseSessions = /* @__PURE__ */ new Map();