fnlowl
Read and manage fnlowl widgets, leads, email sequences and analytics from an AI assistant.
| Endpoint | https://api.fnlowl.com/v1/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.1 |
| Now | 40 tools · grade D (57) · pin ts_6ac64a22dff6f54f5570dcbf7362ba18 · protocol 2025-06-18 |
| First / last listed | 2026-10-26 05:48 UTC / 2026-10-26 05:48 UTC |
| Grade over time | 2026-10-26: D (57), 40 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: list_projects create_project offer_choice read_plan_usage plan_site_strategy list_widgets read_widget create_widget update_widget request_widget_publish start_experiment stop_experiment list_leads read_lead read_analytics list_widget_analytics read_widget_results read_experiment_results list_campaigns draft_campaign update_campaign list_sequences list_sequence_enrollments draft_sequence update_sequence pause_sequence activate_sequence list_templates create_template update_template read_brand update_brand read_ai_context update_ai_context read_sending_status list_email_deliveries list_integrations read_integration_delivery_status read_ai_generation_status ask_question
list_projects | Lists the projects this credential can act on. A project is one site or brand under the account, and every widget, lead, campaign and sequence belongs to one. Pass an id as the project argument on any tool to run that call in it, or as the x-fnlowl-project header (remote) or FNLOWL_PROJECT (local) to set the connection's default; with neither, tools read across the whole account. The row with curr params: none |
create_project | Creates a project — one more site or brand under the account — and returns its id. Pass that id as the project argument (or x-fnlowl-project / FNLOWL_PROJECT) to work inside it. Projects cannot be deleted from here. params: name*, emoji |
offer_choice | Presents the user with a choice between 2 to 4 options, each with a label and a one-line description, one optionally marked recommended. It is for decisions where reasonable options would build different things — which widget kind, what score ranges, what copy or trigger — and nothing the user said settles it. It changes nothing and returns the options for the user to answer. params: question*, options*, project |
read_plan_usage | Reads the account's plan and what it has used of each monthly quota: leads captured, emails sent, AI messages, plus how many websites and widgets exist against the plan's limits. Leads are counted over the billing period and everything else over the calendar month (UTC). `plan` is null when no plan is active. Answers "what is my limit" and "how close am I to the cap". Changes nothing. params: none |
plan_site_strategy | Gives an agent what it needs to advise on a website's lead capture: a snapshot of the website's widgets (kind, live or draft, views, completions, conversion), the six widget kinds with where each appears, and the steps to follow — read the site, ask the user questions with offer_choice, then rank 3-5 fixes. It fetches no pages and changes nothing. Suited to "what should I do on my site" or "audit params: project |
list_widgets | Every widget in the current project, newest last. Returns summaries only — id, name, kind, type, status, article, views, completions. Use read_widget for one widget's full content. params: project |
read_widget | One widget in full, plus `issues` — what is still missing before it could go live. Includes its questions, quiz questions and options, quiz tiers and calculator inputs. Which of those are meaningful depends on the kind: questions for lead-magnet and survey, quiz fields for quiz, calculator inputs for calculator, none for popup and announcement-bar. `placement` says where it shows on a site: popups params: widgetId*, project |
create_widget | Create a widget in the current project. Six kinds: lead-magnet, popup, survey, announcement-bar, quiz, calculator. It is always created as a draft, and the result lists `issues` — what is still missing before it could go live (empty when nothing is); fix them with update_widget. Going live is a separate step, request_widget_publish. What each kind needs (send only name and kind and the rest starts params: name*, kind*, type, article, showOn, showOnValue, hideOnValue, position, headline, description, buttonText, consentText, successHeadline, successMessage, layout, theme, accentColor, backgroundColor, textColor, cornerStyle, logoUrl, placement, popupWidth, floatingButton, buttonStyle, requireEmail, contentUrl, senderName, subject, emailBody, emailFormat, trigger, triggerValue, triggerMode, cooldownDays, maxDismissals, startAt, endAt, rewardType, rewardCode |
update_widget | Change a widget. Only the fields sent are changed, with one exception: sending ANY of questions, quizQuestions, quizTiers or calcInputs replaces ALL FOUR with exactly what is sent, so send the complete set you want to end up with. Publishing is a separate action. Views and completions cannot be set — they are counted from real traffic. The result lists `issues` — what is still missing before it co params: name, kind, type, article, showOn, showOnValue, hideOnValue, position, headline, description, buttonText, consentText, successHeadline, successMessage, layout, theme, accentColor, backgroundColor, textColor, cornerStyle, logoUrl, placement, popupWidth, floatingButton, buttonStyle, requireEmail, contentUrl, senderName, subject, emailBody, emailFormat, trigger, triggerValue, triggerMode, cooldownDays, maxDismissals, startAt, endAt, rewardType, rewardCode |
request_widget_publish | Ask for a draft widget to go live. This requests publication; it does not publish. Called over the API or MCP with a key it does NOT publish: it creates a pending approval carrying a before/after snapshot and returns it, and the widget goes live only when a signed-in person approves it in the dashboard. The result also says where the widget will appear (`placement` — going live does not put a quiz params: widgetId*, project |
start_experiment | Split traffic between a control widget and 1 to 3 variants. The variants must already exist as their own live widgets, of the same kind and project as the control (created with create_widget and made live with request_widget_publish). On a small site one variant at a time is the practical limit: every extra arm needs the same traffic again. Traffic splits evenly unless trafficPcts is given: one wh params: widgetId*, variantWidgetIds*, holdoutPct, trafficPcts, project |
stop_experiment | End a running experiment. Counts stop with it; starting a new one on the same widgets begins with fresh counts, not a resume. params: widgetId*, project |
list_leads | Captured leads for the current project, newest first. PAGED — at most 200 per call, and the limit is a hard cap, not a default you can raise; pass offset for the next page (limit 50 with offset 50 returns leads 51 onward). These rows are real people's email addresses. Each lead carries a quality verdict (good, warn, bad, unchecked) from cheap capture-time checks; bad leads are stored but were neve params: limit, quality, offset, project |
read_lead | One lead with the answers it gave, and its quiz score and tier if it came from a quiz. The score is frozen at the moment of submission — it is what that visitor actually saw, not a recomputation against the quiz as it stands today. params: leadId*, project |
read_analytics | Totals for the current project: widget count, page views, completions, conversion percentage, lead count and how many have unsubscribed. Conversion is completions divided by views as a whole percentage; with no views yet it reads 0, which means NO DATA rather than a failure. Completions is not leads — an announcement-bar or an ungated calculator completes without capturing an address. Pass from an params: from, to, project |
list_widget_analytics | The same numbers per widget, best-converting first. Use this to answer which magnet is working; use widget_results for where one widget's traffic came from. params: project |
read_widget_results | One widget's views, completions, conversion, and its leads grouped by referrer. The referrer is whatever the visitor's browser reported when they submitted, so it is a rough attribution, not a tracked source. Also returns the funnel (views, completions, leads, conversions, revenue in cents; conversions are purchases credited to a lead within 14 days of capture), questionDropoff (how many visitors params: widgetId*, from, to, project |
read_experiment_results | The A/B experiment a widget is in (or last ran as control): per arm, assigned views, leads, conversion rate and 95% interval in basis points (1234 = 12.34%), and lift against the control arm. result "insufficient_data" means at least one arm has too few views for a rate to mean anything; in that case NO rate or lift is given for any arm, so none is available. A running experiment lists every arm, params: widgetId*, project |
list_campaigns | Campaigns in this project, newest first, with their status. Open and click numbers come from the sent-email ledger, not from a counter on the campaign. params: project |
draft_campaign | Create a campaign AS A DRAFT. There is no tool that sends one: sending puts mail in thousands of real inboxes, spends deliverability reputation that cannot be bought back, and cannot be undone. A person sends it from the dashboard. recipientScope is "all" or a single widget id, and unsubscribed or bounced addresses are excluded automatically. params: name*, subject*, body*, recipientScope*, project |
update_campaign | Change a draft campaign. A campaign that has already been sent cannot be edited — the ledger describes what actually went out, and editing it afterwards would make that a lie. params: campaignId*, name, subject, body, recipientScope, project |
list_sequences | Sequences in this project with their steps and branch. The shape is BOUNDED: a linear chain of steps, then at most one branch point, each path its own linear chain. No nesting, no rejoining, no parallel paths. params: project |
list_sequence_enrollments | Who is running through which sequence: for a lead (leadId) or for a sequence (sequenceId), each enrolment's status (active, finished or stopped), the step it is on and when it is next due. This is how to answer "why did this lead get, or not get, the follow-up" — a lead with no enrolment was never enrolled, and activating a sequence enrols future leads, not past ones. At most 100 rows, oldest firs params: leadId, sequenceId, project |
draft_sequence | Create a sequence AS A DRAFT. Steps are either an email or a delay in days — a delay is its own step, so two emails can run back to back. A branch may be added at the end; its paths are evaluated first-match-wins, left to right, and a filter with field null always matches, so it only makes sense last. Filters can only test what a lead already carries: unsubscribed and quizTierLabel. params: name*, widgetId*, steps*, branch*, project |
update_sequence | Change a DRAFT sequence. Only the fields sent are changed, except that sending steps or branch replaces the whole of that part, so send the complete chain you want. It cannot edit an active sequence and cannot activate one: an active sequence is paused with pause_sequence, edited, and started again with activate_sequence. Enrolments already running keep the plan they started with. params: sequenceId*, name, widgetId, steps, branch, project |
pause_sequence | Move a sequence to draft, which stops new enrolments. Stopping mail is never the slower path, so this applies immediately. Starting one again is activate_sequence: an active sequence enrols every future lead and sends on a timer with nobody watching. params: sequenceId*, project |
activate_sequence | Activate a draft sequence so future matching leads are enrolled and may receive its emails. Activation starts timed sending with nobody watching, and the server does not itself verify human confirmation. params: sequenceId*, project |
list_templates | Transactional templates in this account. Built-in starters are marked isCustom false and cannot be deleted. params: project |
create_template | Create a transactional template. category is one of authentication, account, orders, notifications. Use {{name}} placeholders in the subject and body for values supplied when it is sent; a placeholder nobody supplies is replaced with nothing. It creates the template only — sending needs a person. params: name*, category*, subject*, body*, project |
update_template | Change a template's name, category, subject or body — only the fields sent. Built-in starters can be rewritten too (they just cannot be deleted). It changes what later sends of this template say; it sends nothing. params: templateId*, name, category, subject, body, project |
read_brand | The brand: site name, accent colour, sender name, logo and the postal address that every commercial email needs in its footer. With a project in scope this is that website's brand — the account defaults with the website's own overrides applied; without one it is the account defaults. params: project |
update_brand | Change brand settings. Only the fields sent are changed. With a project in scope this sets that website's own override and leaves the account defaults — and every other website — alone; without one it changes the account defaults every website inherits. The accent colour must be a hex value — it is interpolated into a stylesheet that renders on customers' websites. params: siteName, accentColor, senderName, logoUrl, mailingAddress, legalName, termsUrl, privacyUrl, project |
read_ai_context | The account's AI context: what the blog is about, its pricing tiers, value props, testimonials, design direction and tone presets. Every AI-personalised lead magnet is generated from exactly this plus the visitor's own answers. It belongs to the whole account and is shared by every website on it, so a connection limited to one website can read it but not change it. params: project |
update_ai_context | Change the AI context. This is the highest-leverage thing you can write here: it is tedious for a person to fill in and it improves every generation afterwards. Only the fields sent are changed. It holds what the site actually says, so testimonials and prices come from the owner. The AI context belongs to the whole account and is shared by every website on it, so it cannot be changed from a connec params: about, designDirection, valueProps, pricingTiers, testimonials, project |
read_sending_status | Read account sending readiness, domain verification, daily usage, and recent reputation state. While the sending domain is not yet verified it also returns `records`: the DNS records to publish. `sentToday` counts the last 24 hours on a rolling basis, while `sharedTrial.sendsUsed` counts the account's lifetime sends on the shared trial, so the two legitimately differ. Does not send mail. params: project |
list_email_deliveries | List recent email outcomes for this account. Recipients are masked; use this to diagnose queued, delivered, opened, clicked, bounced, complained, or failed mail. `sentToday` counts the last 24 hours on a rolling basis, while `sharedTrial.sendsUsed` counts the account's lifetime sends on the shared trial, so the two legitimately differ. Does not send mail. params: limit, project |
list_integrations | List native integration providers and connection health. Credentials are never returned. params: project |
read_integration_delivery_status | Read recent queued ESP/webhook handoff outcomes and retry state. Lead identifiers, payloads, and credentials are not returned. params: limit, project |
read_ai_generation_status | Read recent AI lead-magnet generation outcomes by status and widget. Visitor answers, generated content, lead ids, and failure details are not returned. params: project |
ask_question | Ask the fnlowl Advisor a question in plain English. It knows how fnlowl works — widgets and where each kind appears, the embed, sequences, campaigns, sending, credits, plans, MCP — and can read the account's own widgets, leads, analytics, campaigns, sequences and sending status to answer. Suited to "how does X work", "why is Y empty" or "what should I do next". It is read-only and spends an AI cre params: question*, project |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.