@leadbay/mcp 0.22.0 → 0.23.1

package/dist/http-server.js

@@ -33,6 +33,204 @@ import {
 } from "@modelcontextprotocol/sdk/types.js";
 
 // src/prompts.generated.ts
+var leadbay_build_campaign = `
+## MEMORY
+
+Before responding, glance at any \`_meta.agent_memory.summary\` returned by tool calls earlier in this session and reflect its top signals in your reasoning ("Filtering by your stated preference for healthcare"). After any material new signal from the user this conversation (sector, region, deal size, communication style, qualification rule, explicit retraction, or recurrence / scheduling preference such as "I do this every day" or "remind me every morning"), call \`leadbay_agent_memory_capture\` to persist it: \`source:"user_stated"\` if literal, \`source:"inferred"\` with confidence <=6 if inferred.
+
+
+Build me a Leadbay campaign from scratch{{arg:campaign_name_paren}}. {{arg:audience_block}}
+
+GATE \u2014 DEFER TO TOOL RENDERING. When you call a Leadbay composite that ships its own RENDERING block (every composite in 0.9.0+ does), render the response using that block's recipe verbatim \u2014 score bars, glyph palette, column order, hide-list, link priorities, all of it. Do NOT substitute prose, a numbered list, or a different column structure even when an orchestrating prompt's body suggests alternate framing. Prompt-specific commentary (motivational nudges, summaries, next-action recommendations) belongs ABOVE or BELOW the canonical table, never in place of it.
+
+If the prompt's body and the tool's RENDERING appear to conflict, the tool's RENDERING wins for the structural layout; the prompt's voice wins for the commentary that surrounds it.
+
+
+# Resilience rules for Leadbay long-running tools
+
+These four rules apply to every Leadbay workflow that calls \`leadbay_pull_leads\`, \`leadbay_bulk_qualify_leads\`, \`leadbay_research_lead_by_id\`, \`leadbay_import_and_qualify\`, or \`leadbay_enrich_titles\`. **Treat timeouts and stream-closed errors as transient, not as signals to replan.**
+
+## Rule 1 \u2014 Pin the lens
+
+After your first \`leadbay_pull_leads\` call, capture \`response.lens.id\` into your working memory and **pass it explicitly as the \`lensId\` argument to every subsequent call** in this session \u2014 including any re-pulls, bulk qualifies, or research calls that accept it. (Field-name caveat: the response nests it as \`lens.id\`; the parameter on subsequent calls is \`lensId\`.) The active lens can shift between calls (5-minute client cache + backend \`last_requested_lens\` can change if the user touches the web UI). A lens shift mid-workflow throws away your top-10 work.
+
+## Rule 2 \u2014 Prefer async for bulk operations
+
+\`leadbay_bulk_qualify_leads\` and \`leadbay_import_and_qualify\` accept \`wait_for_completion:false\`, which returns \`{status:'running', qualify_id}\` immediately. Then poll \`leadbay_qualify_status\` (or \`leadbay_import_status\`) every ~10s until the job completes. **Use the async pattern by default** \u2014 the blocking default can exceed the MCP client's per-call timeout on large batches and produce a misleading \`"Request timed out"\` even though the server is still working.
+
+## Rule 3 \u2014 Serialize \`leadbay_research_lead_by_id\` fan-out
+
+\`leadbay_research_lead_by_id\` is composite and reads many sub-resources. Calling it on 10 leads in parallel can saturate the transport and produce \`"Tool permission stream closed"\` errors that look like permission failures but are really backpressure. **Call it sequentially**, or at most 3 in parallel. If one call fails with a stream/timeout error, retry that one call once before moving on; on a second failure, note the lead and continue \u2014 do not abandon the remaining leads.
+
+## Rule 4 \u2014 Retry, don't replan
+
+If a Leadbay tool returns \`"Request timed out"\`, \`"stream closed"\`, or any other transport-level error (distinct from a Leadbay-issued error payload), the work may still be running server-side. Do this in order:
+
+1. For bulk tools \u2014 retry with \`wait_for_completion:false\` and poll the status tool with the returned id. Don't re-pull leads; that can shift the lens.
+2. For single-lead tools \u2014 retry the same call once. If it still fails, record the lead id and continue with the rest of the workflow.
+3. **Do not** switch strategies (e.g. "the endpoint is broken, let me re-pull from scratch"). The earlier work is still valid; the timeout was the wire.
+
+If \`pull_leads\` itself fails and you have no prior batch, then yes \u2014 retry it, explicitly pass the lensId you captured (if any), and continue.
+
+
+# PHASE 0 \u2014 STATE + AUDIENCE
+
+Call \`leadbay_account_status\` to see my remaining quota, my **enrichment credits**, and my **active lens**. Note \`web_fetch_remaining\` (qualification budget) and the enrichment credit balance \u2014 Phase 3 spends credits.
+
+Resolve the audience:
+
+- **Default \u2014 use my active lens.** If I didn't name a fresh audience, the active lens IS the audience. Do NOT create a new lens.
+- **Fresh-audience fork.** Only if I described a NEW audience the active lens doesn't already cover, set it up first: \`leadbay_adjust_audience\` for sector/size tweaks, or \`leadbay_new_lens\` to create a brand-new named lens \u2014 then continue on that lens. Do NOT silently overwrite my existing lens; confirm once before switching.
+
+# PHASE 1 \u2014 DISCOVER
+
+Call \`leadbay_pull_leads\` on the resolved lens. **Capture \`response.lens.id\` and pass it as an explicit \`lensId\` on every later call this session** \u2014 a mid-session lens shift would discard the cohort I'm about to pick. Render the batch with the canonical layout:
+
+## RENDERING \u2014 markdown table, three columns, score-bar driven
+
+Present the response as a markdown table sorted by \`score\` descending, with exactly three columns. Do not summarize in prose. Do not show the numeric score anywhere.
+
+## Score-bar (10-segment, inline-code wrapped)
+
+Wrap a 10-glyph bar in a SINGLE inline-code span (backticks). The inline-code styling is what gives the bar contrast in most chat renderers \u2014 HTML \`<span>\` is stripped inside table cells.
+
+Glyphs (use these exact characters; do not substitute):
+
+- \`\u25B0\` \u2014 firmographic-only fill
+- \`\u2756\` \u2014 AI-booster cap (placed at the RIGHT END of the filled run, never the front)
+- \`\u25B1\` \u2014 empty
+
+Computation:
+
+\`\`\`
+total_filled  = round(score / 10), clamped to 0..10
+ai_segments   = round(qualification_summary.avg_qualification_boost / 3.3),
+                clamped to [0, total_filled]
+normal_filled = total_filled \u2212 ai_segments
+bar = "\u25B0" \xD7 normal_filled
+    + "\u2756" \xD7 ai_segments
+    + "\u25B1" \xD7 (10 \u2212 total_filled)
+\`\`\`
+
+If \`qualification_summary.answered == 0\` or \`avg_qualification_boost\` is null, set \`ai_segments = 0\` (no \u2756). Always wrap the bar in backticks. Print the legend \`\` \`\u25B0\` firmographic \xB7 \`\u2756\` AI booster cap \xB7 \`\u25B1\` unfilled \`\` once below the table.
+
+
+**Column 1 \u2014 Company**
+
+- Line 1: the 10-segment score bar in inline-code backticks (see the score-bar snippet above for the algorithm).
+- Insert \`<br>\` between lines.
+- Line 2: linked company name + \` \xB7 \` + short location + \` \xB7 \` + compact size.
+  - Link target: \`website\` (prefix \`https://\` if it's a bare hostname). Don't synthesize an app deep-link.
+  - Location: shorten "City of New York" \u2192 "NYC"; otherwise "City ST"; state alone only when city missing.
+  - Size: \`"Xk+"\` when \`size.min >= 1000\`, \`"min\u2013max"\` otherwise.
+
+**Column 2 \u2014 Why it fits**
+
+- One sentence, \u2264 20 words.
+- Synthesize from (in priority order, whichever is present) the lead's \`short_description\`, top 2 \`tags[].display_name\`, and the gist of \`qualification_summary.best_response_excerpt\`. The trim payload does NOT carry the longer \`description\` field \u2014 for that, agent must call \`leadbay_research_lead_by_id\` or \`leadbay_research_lead_by_name_fuzzy\`.
+- Do NOT append \`(boost N)\` \u2014 the \u2756 cap in column 1 already carries that signal.
+- No bullet lists, no line breaks inside the cell.
+
+**Column 3 \u2014 Contact**
+
+\`[Contact name](LINK) \xB7 short job title\`. The \`[Contact name](LINK)\` markdown link wrapping is mandatory \u2014 never render the name as plain text. See linking/contact-linkedin for the URL priority (real profile \u2192 constructed people-search) and the \xB0-flag fallback.
+
+**Hide from the user (never include in any cell):** \`id\`, \`location.pos\`, \`location.country\` (unless city/state both missing), \`sector_id\`, \`is_hq\`, \`web_fetch_in_progress\`, \`enrichment_in_progress\`, \`highlighted_fields\`, \`custom_fields\`, \`contacts_count\` when 0, \`notes_count\` / \`epilogue_actions_count\` / \`prospecting_actions_count\` when 0, \`stale_at\`, \`deal_insights\`, \`social_presence\` booleans (except as the \xB0-flag signal), \`need_attention\` flags, any field whose value is the string \`"null"\`.
+
+## Linking a contact's name
+
+**MANDATORY: every contact name in your output \u2014 table cells, prose, headers, "Reach <Name>" callouts \u2014 MUST be wrapped in markdown link syntax \`[Name](URL)\`. Never render a contact name as bare text. A plain-text name is a broken contact card; the underlined name is the user's primary affordance for "take me to this person's profile". No "no URL available" exception \u2014 the search URL below is always constructable from name + company.**
+
+URL priority (first applicable wins):
+
+1. **Real profile** \u2014 \`contact.linkedin_page\` when it's a string starting with \`https://\` (the MCP coerces the legacy literal \`"null"\` string to real null before you see it).
+2. **Constructed people-search** \u2014 \`https://www.linkedin.com/search/results/people/?keywords=<First>+<Last>+<Company>\`. URL-encode params. Strip Inc / LLC / Corp / Ltd / GmbH / Co / S.A. / S.L. / PLC / AG / SAS / SARL suffixes from the company. Append a trailing \` \xB0\` to the rendered name ONLY when this fallback is in use AND \`social_presence.linkedin == false\`. Never append \`\xB0\` when a real \`linkedin_page\` was used.
+
+Never link a person's name to the company's LinkedIn page (and vice versa) \u2014 the two surfaces are different and conflating them quietly degrades the workflow.
+
+## Linking the company
+
+Use the lead's \`website\` as the company-name link target \u2014 prefix \`https://\` if the value is a bare hostname. (The MCP does NOT synthesize a Leadbay-app deep-link URL; the team has not standardized one. Linking to \`website\` is always real data.)
+
+When the response carries \`social_urls\` (the post-fix multi-platform URL block on rich-lead responses), render every non-null platform as a pill chip in the company-info row. Iterate over \`social_urls\`'s keys \u2014 never hardcode a fixed list \u2014 and emit each as \`[<platform-label>](<url>)\`. Skip platforms whose URL is null.
+
+\`social_presence\` carries booleans for the same 6 platforms (crunchbase, facebook, instagram, linkedin, tiktok, twitter) \u2014 useful when you only care that the company has a profile somewhere. Use it as the \xB0-flag signal in the contact people-search fallback (see linking/contact-linkedin).
+
+
+
+If the batch is thin (fewer than ~10 workable leads) or I ask for more depth, top it up: call \`leadbay_bulk_qualify_leads({lensId:<captured>, count:<deficit, max 25>, wait_for_completion:false})\`, poll \`leadbay_qualify_status\` until done, then re-pull with the same \`lensId\`. Never re-pull without \`lensId\`.
+
+# PHASE 2 \u2014 PICK AN ICP CANDIDATE POOL
+
+A campaign is only as good as the leads in it \u2014 AND only as good as whether each lead has a reachable BUYER (see Phase 3). So pick a **generous candidate pool** now, not the final cohort: aim for ~1.5\xD7 the target size of in-ICP leads (highest \`ai_agent_lead_score\`), so Phase 3 can drop any lead that turns out to have no buyer-persona contact and still hit the target. If the batch is short, top up via \`leadbay_bulk_qualify_leads\` / \`leadbay_extend_lens\`.
+
+If I named specific leads, use those (but still apply the Phase 3 buyer-coverage check and tell me which lack a buyer). Otherwise recommend the pool and show it. Capture the candidate \`leadIds\`. Confirm the count ("12 candidates \u2014 I'll lock the final ~8 after checking each has a buyer"). Do NOT create the campaign yet \u2014 the final cohort is decided after Phase 3's coverage check.
+
+# PHASE 3 \u2014 ENRICH THE RIGHT CONTACTS (load-bearing)
+
+This is the phase that decides whether the campaign is worth a salesperson's time. Contacts aren't attached by default and enrichment is paid \u2014 so spend it ONLY on the people who would actually **buy what I sell**, not on whoever is most senior.
+
+**Step A \u2014 work out MY buyer persona (do this before touching titles).**
+Figure out what *I* sell and therefore who, inside the target company, owns the decision to buy it:
+
+- Infer my product / value-prop from my context: my org and account (\`leadbay_account_status\`), and especially my lens's qualification criteria \u2014 the \`qualification_summary\` on the leads tells you *why* these companies are good targets for me, which implies what I'm offering them.
+- Map value-prop \u2192 the **buying department/persona**, NOT seniority:
+  - A sales / prospecting / lead-gen / outbound / marketing / GTM / revenue tool \u2192 the **revenue org**: VP / Head / Director of Sales, Business Development, Account/Carrier Sales, CRO, CMO / VP Marketing, Head of Growth / Demand Gen, RevOps. (This is Leadbay's own persona.)
+  - An operations / logistics tool \u2192 operations leaders. A finance tool \u2192 finance. A dev tool \u2192 engineering. Etc.
+  - **Company size caveat:** Founder / CEO / Owner is a real buyer at small companies (\u2264~50), but at larger ones they are not \u2014 there the functional leader (e.g. VP Sales) is the buyer.
+- **State the persona in one line and confirm it with me** before spending (see Step C). I can correct it.
+
+**ANTI-PATTERN \u2014 do NOT do this:** picking the most senior or most "decision-maker-sounding" title regardless of department. A Director of Operations, COO, Mgr of Logistics, CFO, or CTO will **never** buy a sales tool \u2014 enriching them wastes credits and hands me a useless list. Seniority is not the same as being my buyer.
+
+**Step B \u2014 find the persona-matching, enrichable contacts.**
+Call \`leadbay_recall_ordered_titles({leadIds, lensId})\` and \`leadbay_enrich_titles({leadIds, lensId})\` in **discovery mode** (no \`titles\`). These return previously-enriched titles, \`title_suggestions\`, \`auto_included_titles\`, \`available_in_selection\`, \`enrichable_contacts\`, and \`credits_remaining\`. Treat them as a **menu to filter against my persona \u2014 not the answer.** If past-enriched titles or suggestions are off-persona (e.g. operations roles for a sales tool), do NOT repeat them. Select the titles that match my buyer persona AND are actually enrichable.
+
+**Step B.5 \u2014 coverage guarantee (lock the final cohort here).** A campaign where half the leads have no buyer is a failed campaign. So before enriching, determine for each candidate lead whether it actually has an **enrichable buyer-persona contact** \u2014 use the discovery data plus, where it's ambiguous, a quick \`leadbay_research_lead_by_id\` to see that lead's available contact titles. Then:
+
+- **KEEP** candidates that have \u22651 enrichable buyer-persona contact.
+- **SWAP OUT** candidates whose only contacts are off-persona (e.g. ops/dispatch/finance only) or who have no enrichable contact at all. Replace each with the **highest-\`ai_agent_lead_score\` in-ICP candidate** from the pool that DOES have a buyer, until the cohort hits the target size (default 20; here capped by the enrichment budget).
+- **Do NOT trade ICP fit for coverage.** A lead with a buyer but weak ICP fit (low \`ai_agent_lead_score\`, a vertical that doesn't match what I sell) is still the wrong lead \u2014 coverage is a filter applied AFTER ICP, never a reason to admit an off-ICP company. The final cohort must be both high-ICP AND buyer-covered.
+- If the lens genuinely can't supply enough buyer-ready, in-ICP leads, say so honestly and offer to widen/extend rather than padding the campaign with no-buyer leads OR with off-ICP ones.
+
+Tell me what you swapped in one line ("dropped Corbett + RBS \u2014 ops-only; swapped in Acme + Globex which have Sales VPs"). The goal is a final cohort where EVERY lead has a real buyer to call.
+
+**Step C \u2014 show the spend + persona and confirm.** State the persona, the chosen titles, and "You have {credits_remaining} credits; this enriches {enrichable_contacts} contacts." Confirm via \`ask_user_input_v0\` ("Enrich these {enrichable_contacts} <persona> contacts now?" \u2192 ["Yes, enrich", "No, skip", "Change the persona/titles"]). Never launch a paid run without this. Enrich up to the campaign size (default 20) best persona-matching contacts.
+
+**Step D \u2014 launch + poll.** On yes: \`leadbay_enrich_titles({leadIds, lensId, titles:[...chosen], email:true, phone:true})\` to launch, then poll \`leadbay_bulk_enrich_status\` until done (enrichment can take several minutes \u2014 keep polling, don't render an empty sheet prematurely). Append one small line at the very end of your reply: \`_(N credits remaining)_\`.
+
+If I skip enrichment, continue \u2014 the campaign can be enriched later from the call sheet.
+
+# PHASE 4 \u2014 CREATE THE CAMPAIGN
+
+Derive a name (\`<lens or audience> \u2013 <today's date>\`) or use the one I gave. Call \`leadbay_create_campaign({name, lead_ids:<final buyer-ready cohort from Phase 3>})\` \u2014 this creates AND seeds in one call. Seed the cohort you actually enriched buyers on, not the original raw pool. Confirm the returned campaign name + id in one line. (If I later ask to add more leads to it, that's \`leadbay_add_leads_to_campaign\`.)
+
+# PHASE 5 \u2014 THE VIEW (call / email ready)
+
+If you launched enrichment in Phase 3, **poll \`leadbay_bulk_enrich_status\` until it's actually done before rendering** \u2014 do not render a "still enriching" sheet with empty contact cells; the whole point is the landed phones/emails. Enrichment can take several minutes; keep polling.
+
+Then call \`leadbay_campaign_call_sheet({campaign_id})\` and render it per its RENDERING block \u2014 one card per lead, contacts with \`[phone](tel:)\` + \`[email](mailto:)\` one-tap links, the readiness chip at the top, map optional. This is the view I work from: scan \u2192 tap to call \u2192 tap to email.
+
+**Flag suspect contacts** so I don't email the wrong person blind: mark with \u26A0 any enriched contact whose email domain doesn't match the company's website, or who shows up on more than one lead in this campaign (a sign of a mis-attributed enrichment). Keep the phone (it's usually still right) but tell me the email looks off.
+
+# PHASE 6 \u2014 HANDOFF + STOP
+
+The campaign exists and is call/email ready. End by offering, via \`ask_user_input_v0\`:
+
+- "Start working it now" \u2192 run \`leadbay_work_campaign\` on this campaign (the calling/email session + outcome-logging loop).
+- "See the pulse" \u2192 \`leadbay_campaign_progression\` for per-lead status.
+
+Then STOP. Building a campaign is NOT outreaching \u2014 do not send anything and do not call \`leadbay_report_outreach\`. When I come back later to log calls, see previous statuses, and do follow-ups, that is \`leadbay_work_campaign\`, not this prompt.
+
+# Iron laws
+
+- Enrichment targets MY buyer persona \u2014 the people who would actually buy what *I* sell, derived from my product/ICP \u2014 NOT generic seniority. For a sales/prospecting tool that means the revenue org (sales / BD / growth / marketing leaders); a Director of Operations, COO, or logistics manager is useless no matter how senior. Get the persona right or the campaign is worthless.
+- Selection is DATA-DRIVEN (\`leadbay_recall_ordered_titles\` + \`leadbay_enrich_titles\` discovery) but FILTERED to the persona \u2014 never blindly repeat past-enriched or suggested titles that don't match who buys my product.
+- The FINAL cohort must be all buyer-ready: drop/swap any lead with no enrichable buyer-persona contact (Phase 3 Step B.5) rather than shipping it empty. A campaign where half the leads have no buyer to call is a failed campaign. Pick a generous pool in Phase 2 so swaps are possible.
+- NEVER launch paid enrichment without showing \`credits_remaining\` + \`enrichable_contacts\`, naming the persona, and getting a yes.
+- Qualify / pick BEFORE \`leadbay_create_campaign\` \u2014 never seed a campaign with unvetted leads.
+- Carry the captured \`lensId\` on every call. A lens shift loses the cohort.
+- End at the rendered call sheet, then hand off to \`leadbay_work_campaign\`. Do NOT re-implement the calling / follow-up loop here, and do NOT call \`leadbay_report_outreach\`.
+`;
 var leadbay_daily_check_in = `
 ## MEMORY
 
@@ -1057,6 +1255,7 @@ Optional: offer to review the \`leadbay_campaign_progression\` for the same camp
 - If the user dictates an outcome that doesn't cleanly map to one of the four epilogue values, ASK ONCE before guessing.
 `;
 var PROMPT_META = {
+  leadbay_build_campaign: { "name": "leadbay_build_campaign", "short_description": 'Build a sales campaign from scratch in one guided flow: discover on the\nactive lens, qualify and pick a cohort, enrich the contacts most likely to\nengage, save it via `leadbay_create_campaign`, then show a one-tap call/email\nview via `leadbay_campaign_call_sheet`. Trigger on "build me a campaign",\n"set up a new campaign", "create a campaign from scratch". WORK an existing\ncampaign with `leadbay_work_campaign`; split leads across reps with\n`leadbay_setup_team_prospecting`.\n', "arguments": [{ "name": "audience", "description": "Optional: a fresh audience to target (e.g. 'dental clinics in Texas'). Omit to build from your ACTIVE lens \u2014 the default.", "required": false }, { "name": "campaign_name", "description": "Optional: a name for the campaign. Omit and one is derived from the lens/audience + date (or the backend AI-names it).", "required": false }], "expected_calls": ["leadbay_account_status", "leadbay_pull_leads", "leadbay_bulk_qualify_leads", "leadbay_qualify_status", "leadbay_recall_ordered_titles", "leadbay_enrich_titles", "leadbay_bulk_enrich_status", "leadbay_create_campaign", "leadbay_add_leads_to_campaign", "leadbay_campaign_call_sheet", "leadbay_campaign_progression", "leadbay_new_lens", "leadbay_adjust_audience"], "failure_modes": ["Enriches by seniority instead of by buyer persona \u2014 picks COO / Director of Operations / Mgr of Logistics / CFO / CTO because they sound senior, when the user sells a SALES tool whose buyer is the revenue org (VP/Head/Director of Sales, BD, growth, marketing). Operations people never buy a sales tool; this hands the salesperson a useless list.", "Fails to derive the user's buyer persona from their product/ICP before choosing titles \u2014 jumps straight to titles without working out who buys what THIS user sells, then defaults to generic exec titles.", "Blindly repeats leadbay_recall_ordered_titles / discovery suggestions even when they are off-persona (e.g. operations roles a prior session wrongly enriched) \u2014 recall is a filtered input, not the answer.", "Poor coverage \u2014 leaves many picked leads with no persona-matching contact (or 0 enrichments on some leads) and doesn't flag it, so the salesperson opens the campaign to half-empty rows.", "Launches paid enrichment without first showing credits_remaining + enrichable_contacts, naming the persona, and getting a yes \u2014 the spend-visibility gate is mandatory.", "Creates the campaign before qualifying / picking \u2014 seeds a campaign with unvetted leads. Qualify and let the user pick (or AI-recommend) FIRST, then leadbay_create_campaign.", "Ends at 'campaign created' without rendering the leadbay_campaign_call_sheet view \u2014 the ready-to-work view IS the deliverable; stopping short is purpose drift.", "Re-implements the calling / outcome / follow-up loop instead of handing off to leadbay_work_campaign \u2014 that prompt already owns it. This prompt BUILDS; work_campaign WORKS.", "Auto-sends outreach or calls leadbay_report_outreach \u2014 building a campaign is not outreaching. No send, no log; the user works it afterward.", "Re-pulls leadbay_pull_leads without the captured lensId \u2014 a mid-session lens shift discards the picked cohort.", "Silently overwrites the user's active lens when forking to a fresh audience \u2014 confirm once before switching lenses.", "Renders the picked leads or the call sheet as prose instead of the canonical per-tool RENDERING layout."] },
   leadbay_daily_check_in: { "name": "leadbay_daily_check_in", "short_description": 'Morning DISCOVERY workflow \u2014 new leads from the lens wishlist. Trigger\non "show me leads", "what\'s new today", "let\'s prospect", "run my check-in",\n"my morning check-in", "I do this every day", "every morning". Recurrence\nlanguage always means this prompt. Do NOT trigger on follow-up phrasings\n("follow up", "before my trip") \u2014 those go to `leadbay_followup_check_in`.\n', "arguments": [], "expected_calls": ["leadbay_account_status", "leadbay_pull_leads", "leadbay_research_lead_by_id", "leadbay_bulk_qualify_leads", "leadbay_enrich_contacts"], "failure_modes": ["Calls leadbay_report_outreach without explicit user authorization", "Surfaces fewer than 10 leads when more are available, or fails to top up via leadbay_qualify_top_n when the batch is short", `Replaces the canonical pull_leads table layout with prose per row (the per-tool RENDERING block is the structural contract; "Today's nudges" goes above it, not in place of it)`, "Skips the nudge paragraph entirely \u2014 the table alone is fine but adding the nudge is the value-add", `Skips deep research on promising leads (Phase 4) \u2014 the agent must call leadbay_research_lead_by_id on each when the user's intent is to research specific leads; Phase 4 is intentionally skipped for batch-view requests ("show me today's leads", "run my morning check-in") per the Phase 4 skip gate`, "Triggers contact enrichment without asking the user first (it consumes quota)", "Skips the STOP byproduct and proposes next actions on its own", 'Fires 10 parallel leadbay_research_lead_by_id calls and treats "stream closed" errors as terminal \u2014 must serialize and retry singletons', "Re-pulls leadbay_pull_leads without passing the captured lensId, allowing a backend lens shift to discard the Phase 2 batch", 'Treats a "Request timed out" from leadbay_bulk_qualify_leads as terminal instead of retrying with wait_for_completion:false + qualify_status polling', 'Triggers on a follow-up query (e.g., "leads I should follow up with") that should have routed to `leadbay_followup_check_in` \u2014 the two entry points are different data sources (Discover wishlist vs Monitor view) per \xA71.6'] },
   leadbay_extend_my_lens: { "name": "leadbay_extend_my_lens", "short_description": "Add more leads to the current lens on demand \u2014 for users whose appetite\nexceeds the standard daily fill. The agent picks seeds silently from\nwhat's already on the lens, fires the extra refill, and surfaces the\nqueue confirmation. The user never reviews the seed list.\n", "arguments": [{ "name": "extra_count", "description": "How many extra leads to add. Optional. Omit to use the backend default.", "required": false }], "expected_calls": ["leadbay_account_status", "leadbay_seed_candidates", "leadbay_extend_lens", "leadbay_pull_leads"], "failure_modes": ["Surfaces the seed candidate list to the user instead of picking silently \u2014 the user asked for MORE LEADS, not a candidate review meeting", "Skips the seeded path and calls `leadbay_extend_lens` with no `seed_lead_ids`, losing the bias signal the recommender needs", "On 429, silently retries instead of surfacing the three options (smaller / wait / upgrade) via your host's choice widget (`ask_user_input_v0` or `AskUserQuestion`)", "Forgets to pre-check `LENS_EXTRA_REFILL` quota in `leadbay_account_status` and burns a wasted API call", "Skips the post-queue pull-leads suggestion, so the user doesn't see what just got added"] },
   leadbay_followup_check_in: { "name": "leadbay_followup_check_in", "short_description": 'Follow-up check-in: surface KNOWN leads from the Monitor view needing\nre-engagement. Trigger on "follow up", "already known leads", "what\'s\noverdue", "before my trip", "who should I re-engage". Do NOT trigger on\n"show me today\'s leads", "my morning check-in", "run my check-in",\n"I do this every day", "every morning" \u2014 those go to\n`leadbay_daily_check_in`.\n', "arguments": [], "expected_calls": ["leadbay_pull_followups", "leadbay_research_lead_by_id", "leadbay_prepare_outreach"], "failure_modes": ["Calls leadbay_pull_leads (the Discover entry point) instead of leadbay_pull_followups \u2014 these are different data sources; the Discover queue does NOT contain Monitor's known-but-cold pipeline", 'Iterates pages of leadbay_pull_leads filtering by engagement_count to "fake" a follow-up view (a real bug observed in 0.9.0 \u2014 the right move is to call pull_followups directly)', "Replaces the canonical pull_followups table layout with prose per row (the per-tool RENDERING block is the structural contract; commentary belongs above or below)", 'Skips the cross-mode pivot offer at the end ("Want to see NEW leads from your wishlist instead?" routes to leadbay_pull_leads)'] },
@@ -1078,6 +1277,7 @@ should I follow up on" to "I'll send via lemlist".
 };
 var PROMPT_CATALOG_HEADER = `This server exposes the following workflow prompts via \`prompts/list\` and \`prompts/get\`. Some MCP clients render them as slash commands; if your client does not, you (the agent) should invoke them directly via \`prompts/get\` when the user's request matches one of the triggers described below.`;
 var PROMPT_CATALOG_BULLETS = {
+  leadbay_build_campaign: `- \`leadbay_build_campaign\` (optional args: audience, campaign_name): Build a sales campaign from scratch in one guided flow: discover on the active lens, qualify and pick a cohort, enrich the contacts most likely to engage, save it via \`leadbay_create_campaign\`, then show a one-tap call/email view via \`leadbay_campaign_call_sheet\`. Trigger on "build me a campaign", "set up a new campaign", "create a campaign from scratch". WORK an existing campaign with \`leadbay_work_campaign\`; split leads across reps with \`leadbay_setup_team_prospecting\`.`,
   leadbay_daily_check_in: `- \`leadbay_daily_check_in\`: Morning DISCOVERY workflow \u2014 new leads from the lens wishlist. Trigger on "show me leads", "what's new today", "let's prospect", "run my check-in", "my morning check-in", "I do this every day", "every morning". Recurrence language always means this prompt. Do NOT trigger on follow-up phrasings ("follow up", "before my trip") \u2014 those go to \`leadbay_followup_check_in\`.`,
   leadbay_extend_my_lens: `- \`leadbay_extend_my_lens\` (optional args: extra_count): Add more leads to the current lens on demand \u2014 for users whose appetite exceeds the standard daily fill. The agent picks seeds silently from what's already on the lens, fires the extra refill, and surfaces the queue confirmation. The user never reviews the seed list.`,
   leadbay_followup_check_in: `- \`leadbay_followup_check_in\`: Follow-up check-in: surface KNOWN leads from the Monitor view needing re-engagement. Trigger on "follow up", "already known leads", "what's overdue", "before my trip", "who should I re-engage". Do NOT trigger on "show me today's leads", "my morning check-in", "run my check-in", "I do this every day", "every morning" \u2014 those go to \`leadbay_daily_check_in\`.`,
@@ -1225,6 +1425,30 @@ var CATALOG = [
       )
     ]
   },
+  {
+    name: "leadbay_build_campaign",
+    description: PROMPT_META.leadbay_build_campaign.short_description,
+    arguments: [
+      {
+        name: "audience",
+        description: "Optional: a fresh audience to target (e.g. 'dental clinics in Texas'). Omit to build from your ACTIVE lens \u2014 the default.",
+        required: false
+      },
+      {
+        name: "campaign_name",
+        description: "Optional: a name for the campaign. Omit and one is derived from the lens/audience + date (or the backend AI-names it).",
+        required: false
+      }
+    ],
+    render: (args) => [
+      userMessage(
+        substitutePlaceholders(leadbay_build_campaign, {
+          audience_block: args.audience ? `Target audience: **${args.audience}** \u2014 if my active lens doesn't already cover it, set it up first (confirm before switching lenses).` : "Use my active Leadbay lens as the audience.",
+          campaign_name_paren: args.campaign_name ? ` named **${args.campaign_name}**` : ""
+        })
+      )
+    ]
+  },
   {
     name: "leadbay_setup_team_prospecting",
     description: PROMPT_META.leadbay_setup_team_prospecting.short_description,
@@ -6310,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",
@@ -6333,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"
 ]);
 
@@ -7182,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.
@@ -7585,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.
@@ -7615,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.
@@ -9777,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.
@@ -10003,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\`.
@@ -13908,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: {
@@ -13933,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",
@@ -13968,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");
       }
@@ -14000,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",
@@ -16364,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",
@@ -21314,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
@@ -21407,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,
@@ -22831,7 +23750,7 @@ function parseWriteEnv(env = process.env) {
 }
 
 // src/http-server.ts
-var VERSION = true ? "0.22.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();