Kenso MCP tools
Kenso (formerly Ken AI): the same MCP server, at the same URL.
The Kenso MCP server at https://mcp.ken.so/mcp runs Kenso's cold email and LinkedIn outbound platform from an AI client: campaigns, contacts, people and company search, the inbox, domains and analytics. Sign in with your Kenso account (OAuth), or send Authorization: Bearer <Kenso API key>.
To connect Claude Code: claude mcp add --transport http kenso https://mcp.ken.so/mcp. A connection you already named ken keeps working: the URL is unchanged.
For an agent that should only read, connect to https://mcp.ken.so/mcp/readonly (or add ?readonly=true): it lists no tool that writes and refuses any write, whatever your role.
Each tool takes an operation argument. Its page lists every operation a workspace member can call, the Kenso API route behind it and its parameters.
- Account
account- The caller's own account. My alerts (which events notify me by email, in app, Slack or Teams): get-notification-preferences, with event to read only those events (event="interested" for interested replies), then update-notification-preferences. - Account Signals
account_signals- What changed at a target account's company (funding, hiring, new leaders, headcount, stakeholder job changes, news). A company's current tech stack, brand and funding by domain is saved_searches(operation="company-data-get", domain), not an operation here. Not trigger signals: those are triggers. Also the tier ladder that places target accounts in tiers, and the Accounts lane numbers. Also a contact's or person's behavior signals from outreach outcomes (contact-behavior-get, person-behavior-get). list reads one account's signals; list-workspace reads them across all accounts. Also starting and cancelling a ranked warm path to someone at an account (warm-paths-start, warm-paths-cancel); the paths themselves are committee warm-paths-list and warm-paths-person. - Account Touches
account_touches- Planned 1:1 actions on target accounts: emails, LinkedIn notes, calls and tasks, and each account's 90-day touch plan (plan-* operations). A person approves sends in the Kenso app or by clicking the card approvals_review shows; approved touches then send from the account's Sends from inbox or LinkedIn. client_approvals touches-approve and touches-retry approve as you, only when the person asked for that touch. contact-limits-get returns the guardrails your touch writes must pass. Contact limit collisions list the touches and campaign steps that break a contact limit, and fix one. - Account Views
account_views- Personal saved filters for the Accounts list, one set per member: each view is a named list of filter conditions for the accounts search operation. - Accounts
accounts- Target companies you work one to one (the Accounts lane): accounts, their domains and stakeholders. People are the people tool; your own Kenso user is the account tool. For a brief on an account or to prep a call or meeting with it, call knowledge with operation="context" first (its account_id), not get. Counts and filtered lists: search (include_total=true for a total). Not the workspace's company records: a company by name or domain is contacts companies-list. - Agent Permissions
agent_permissions- What Ken may do on its own in the workspace, per action: asks_first (Ken asks a person first) or runs_on_its_own (no per-item approval; every other guard stays). update changes only the actions it names, after the user says yes; switching send_email or send_linkedin to runs_on_its_own is for a person in the Kenso app only. Needs the agent_permissions flag. - Agent Team
agent_team- Run Kenso's agent templates from your own AI tool: read each live campaign's lead runway and inbox health. Change campaigns only through these operations, and leave everything else as proposals for a person to approve in Kenso. - Agent Work
agent_work- Who runs each kind of Kenso AI work that can wait: Kenso's AI (kenso_ai) or the workspace's own coding agent (my_agent), which collects it with kenso work run. settings-update switches only the kinds it names. get, create-claim, submit-answers and release-claim do that work by hand: read what waits, take a claim, answer it, give the rest back. Needs the agent_work flag. sandbox-connections-list shows the agents connected in the person's own Kenso sandbox; they connect one in the app. sandbox-runs-* run that sandbox, which works the queue with a connected agent; estimate first. sandbox-auto-runs-get shows whether Kenso may start the person's sandbox by itself. - Analytics
analytics- Campaign reports, plus experiments: what Ken noticed in the workspace's campaigns, graded by proof (proven, leaning, hunch, measured, cant_tell). experiments-get reads a finding as text by default; repeat its proof words. experiments-make-default and experiments-undo-default change a live sequence and need confirm=true. load_skill('campaign-diagnosis') has the phrasing rules. How one campaign or the workspace did over dates (sends, replies, positive replies, rates; a daily series is group_by day): get-campaign-performance (from_time, to_time; group_by campaign or day; channel email or linkedin). get-counts only when the request asks for event counts: it counts one campaign's events by event type. A placement test's full results: placement-tests-get with test_id. - Analytics Campaign
analytics_campaign- Not for one campaign's event counts between two dates: that is analytics(operation="get-counts", campaign_id, from_time, to_time). query: metric series and breakdowns, metrics from contacted, sent, delivered, bounced, clicked, replies, interested, meetings, invites, accepted and their rates; group_by up to 2 of campaign, segment, step, variant, channel, inbox, day, week, ...; filters {campaignId: [id], channel: ["linkedin"], ...}; window {preset: last_7_days} or {from, to}. It has no campaign_id or date fields; a daily series to chart is group_by day. dashboard is the workspace view (view summary, chart or campaigns). sending-capacity-get-forecast: the sending forecast of every campaign. - Analytics Events
analytics_events - API Keys
api_keys - Approvals
approvals- approval-tests-create makes an approval draft from a saved search (saved_search_id) or filters. Placement tests are created and listed here; one test's results are analytics placement-tests-get (test_id). - Billing
billing- The workspace's plan, credits, usage and spend limits. Its plan usage (enrichment, emails) between two dates: usage-get with from_time and to_time. AI cost is db ai_spend. It reads only the caller's own workspace. - Blitz
blitz- People, companies, a company's decision-makers and job postings from Blitz, on the workspace's own Blitz API key: every row spends that Blitz plan's records, never Kenso credits, and Blitz returns no emails. Import the people you pick with contacts contact-imports-create, source blitz. Not Kenso Search. - Bug Reports
bug_reports- File a bug report about Kenso for the Kenso team, with optional files. Only after the user explicitly says yes to the drafted report. notes-create adds the user's later words to a report filed in the last 24 hours, instead of filing it again. - Calendar
calendar- Open meeting times. With no provider, a member whose Google or Outlook calendar is connected to Kenso gets times from their own calendar; anyone else names a provider (calendly, cal_com, hubspot). calendar-accounts-list shows the member's connected calendar accounts (up to three) and their calendars. optiverse-connection-get shows whether the member's own Optiverse is connected. granola-connection-get shows whether your own Granola is connected and when it last found a call. The calendar-meeting-type operations edit the member's own list of the types Ken sorts their calendar events into; Scheduler's bookable meeting types are the scheduler tool's. - Calling
calling- The built-in dialer's setup: calling settings, US and Canadian numbers bought for credits, what a call costs and the monthly calling spend limit. Calls themselves are placed in the Kenso app. Also outside dialers (Aircall, Ringover, a signed dialer webhook) and their members (dialer-*). - Campaign Flow
campaign_flow- Two checks: get-workflow-readiness, can a campaign start its enrichment and AI workflows; get-launch-readiness, can it launch sending, what blocks it and how many emails a day it would send. A campaign's AI prompts are prompts(operation="list", campaign_id), not campaign-templates-*, which are saved setups to start new campaigns from. - Campaign Ops
campaign_ops- restart re-runs a campaign's processing from the beginning (after a config change or a stall); reset_processing_status only clears a stuck flag. status is lifetime totals, no date window. campaign_linkedin_url_mismatches lists leads whose LinkedIn URL does not match their name. Stopping a campaign's processing or AI is campaigns pause, not an operation here, and it needs no status read first. - Campaigns
campaigns- A campaign's AI prompts: prompts(operation="list", campaign_id), alone. pause stops a campaign's sending, processing and AI workflows together: call it directly to stop any of them. resume starts a Draft (enrichment, verification and AI workflows; spends credits) or resumes a paused campaign; launch starts sending. update takes flat fields: auto_launch_when_ready=true launches it once Ready; sending_days with a weekend day needs confirm_weekend_sending=true and sending_days_requested_by (who asked, where, when). duplicate with include_contacts=true copies the leads. A read by campaign_id needs no check that the campaign exists: an unknown id comes back not found. Who clicked its links, by name: contacts search with campaign_ids=[id], sort="totalClicks", direction="desc". Its links and UTM tags: tracking_links tracking-links-list. - Claim Links
claim_links - External Approvals
client_approvals - Cloud Files
cloud_files- The caller's own files: Google Drive files they chose for Ken (or Kenso made) and their own OneDrive. search finds files; content returns a document's text (Docs, Sheets as CSV, Slides, PDF, Word, PowerPoint, Excel) or an image's details. Read-only; needs the connected_app_reads flag. - Committee
committee- A target account's buying committee: who decides, who signs, open seats and coverage, plus Ken's mapping runs, an account's research dossier (research), its website, LinkedIn and careers page links (accounts-links) and its hand-off. Stakeholder edits are in the accounts tool. - Contacts
contacts- The workspace's campaign contacts and their company records. To change several contacts, call search once: search(operation="contacts-bulk-update", items=[{"contactId": 1, "outreachLanguage": "de-DE"}, ...]), never update per contact. search, not list, takes campaign_ids, ready_only, filters and sort. Who clicked a campaign's links, by name: search with campaign_ids, sort="totalClicks", direction="desc". A company record by name or exact domain: companies-list. An attached CSV, as is: contact-imports-create with source csv and csv_content. Export: contact-exports-create with campaign_id (campaign_ids for several). Copy another campaign's contacts in: contact-imports-create with source campaign and source_campaign_id, no reads first. create adds rows listed in the message. Delete several contacts in one call: bulk-delete with ids. - CRM
crm- The workspace's CRM connection (HubSpot, Salesforce and more): status, sync health, field map and record lookup, plus Import now and which new CRM contacts become people. Connecting and the other sync settings stay in the Kenso app. Also an ad platform's terms attestation (ad-connections-update) and an ad audience's lift against its holdout (ad-audiences-lift); the rest of ad audiences is integrations. list-lookalike-seeds suggests seed companies for a lookalike company search: customers, CRM closed-won deals or companies that replied Interested. - Domain Orders
domain_orders - Domain Setup
domain_setup- Domain and inbox setup. move_workspace moves domains between workspaces: source_client_id, target_client_id, domain_ids (a list, never domain_id), dry_run. placement-tests-availability says whether a Kenso placement test can run and how many are left; delivery-settings-get and -update hold the placement auto-pause; delivery-defaults-get and -update hold the redirect, senders, reply forwarding and signature new domains and mailboxes start from. - Domains
domains- update and bulk-update take changes (tracking, ramp-up, ...). Several domains: one bulk-update with ids and changes, never update per domain. One domain's id by name: list with q (part of the name). - Email Copy
email_copy - Email Sequences
email_sequences- Campaign and segment email sequences. preview needs use_random: false with a contact_id, true to pick one. segment-email-sequences-delete removes a segment's sequence entirely. - Facebook
facebook- Personal Facebook accounts a workspace sends from: connect and reconnect through a hosted login, time zone, working hours, the mutual-friend floor and the per-action ramp, pause and resume, remove. Each account costs 1,500 credits a month. Nothing here reads the account's chats, friends or posts. - Files
files - Free Tools
free_tools- Kenso's free tools from ken.so/tools: list cleaners, copy checks, spintax, outbound calculators, domain and DNS checks and records, blacklist and SMTP tests. Each operation takes kind and input; calls count against your Kenso account's free limits and every result carries source_url, the tool's page. - Inboxes
inboxes- Connected sending inboxes. create connects an SMTP/IMAP inbox (email, password). Pause, limits and other settings: update, or bulk-update for several (changes). Find inboxes by part of the email (a domain, hello@), sender display name or name: list with q, one call instead of paging the list. - Infra
infra- Fleet cleanup of sending infrastructure: billing leaks, idle or expiring domains, disconnected inboxes and renewal shortfalls. Pausing or changing one inbox or domain is inboxes or domains update. Findings: summary and findings read them; snooze, ignore and reopen change their status (nothing changes at a provider). Fixes: bulk inbox and domain actions (pause, resume, daily limit, connection check, link domain, delete, provider cancel, domain auto-renew off): preview first and show the user what changes, what is skipped and which live campaigns lose sending, then run with the preview token; batches and batch follow it. A batch that takes sending from a live client campaign needs that client's yes first. These work per workspace (needs the infra_findings flag) and for Kenso staff across workspaces; the fleet lists inboxes, domains and provider-accounts, and sweep, are for Kenso staff. - Instagram
instagram- Instagram accounts a workspace sends from: connect and reconnect through a hosted login (connect-sessions; pass instagram_account_id to reconnect), name, daily cap, time zone, working hours, pause and resume (update with paused), remove. Shows today's use per action against the ramp-lowered cap. Nothing here reads the account's chats, followers, following or posts. - Integrations
integrations- Every integration Kenso shows (CRMs, mailboxes, LinkedIn, enrichment, AI clients): whether it is live, your connection and its on/off options. Connect and disconnect with each integration's own tool. Also Google Ads and Meta Ads audiences synced from a campaign's leads (ad-audiences-*, ad-connections-*), and recruiting ATS connections, job imports and candidate pushes (ats-*). - Job Postings
job_postings- Job postings from public ATS boards. search is one call with the request's titles and places in body, as {"titles": {"include": ["VP Sales"]}, "location": {"countries": ["DE"]}}. resolve-filters is autocomplete for half-typed text (body {"titles": "account ex"}), not a step before search: whole titles and places go straight into search. linkedin-job-searches-create searches LinkedIn itself (the user's seat, else Kenso's data provider for credits) with ken-jobs merged in. - Jobs
jobs- Status, results and cancel of Kenso jobs (contact imports and exports, crawls, ...); job_type is required. - Ken Chats
ken_chats- The Ken pane's chat history, shared in the workspace: list chats, read a chat's messages, and delete a chat. The ken-follow-ups operations are Ken checking back on a change made in Ken chat, and reminders: the caller's own pending ones. The ken-slack-reports operations list and stop the caller's recurring Slack reports. Workspace admins only; needs the ken_agent feature flag. - Knowledge
knowledge- What Kenso knows about this workspace, its users and its accounts, with a source on every item. Call context first: one call returns the cited pack for an account or person. Use search only for what the pack does not cover. To edit a file, get it, then update with its version as base_version. Where you cannot edit, use suggestion-create. - Knowledge Library
knowledge_library- Knowledge library: make, rename, move and delete Knowledge folders, upload a file (PDF, Word, slides, a spreadsheet, an image or text) into the company folder, and download a finished export. folders-delete deletes everything below the folder and needs confirm=true. Write markdown with knowledge create instead of uploading it. - Knowledge Prompts
knowledge_prompts- Knowledge prompts: the workspace's qualification, scoring, research, personalization and replies prompts, each applied to everyone, an account tier (1 to 10) or a campaign segment. For each lead the most specific one of a type wins: segment, then tier, then everyone. Research has no segment (account tier, else everyone) and the reply agent always gets the everyone prompt. campaign-resolution-list shows what each segment of a campaign gets. link-knowledge-prompt links an AI variable to a prompt (copying its body); a workflow AI step links one through with.knowledgePromptId in its draft. A body update then rewrites every linked AI variable and draft step still synced to it; usedIn lists both. - Knowledge Review
knowledge_review- Knowledge Review: decide the changes Ken, members and agents suggest, read the change log and undo a change, and set how much Ken applies without review. Accept or dismiss one suggestion, or bulk accept a file's or one source's. settings-update with auto_approve_paused false lifts the spot-check pause. Export Knowledge as a zip, or draft skills from a member's last hand tasks. tree-get reads every folder and file in one call, bodies only on request. upload-content reads the original of an uploaded file. The sources-* operations list, turn on, turn off and disconnect what Ken learns from (your mail and calendars, HubSpot, watched pages). - Knowledge Skills
knowledge_skills- Import an Agent Skill into Knowledge > Skills from a skills.sh link, a public GitHub link or pasted SKILL.md text, and read an imported skill's reference files. skill-imports-create previews first (dry_run, the default): it reads the source and writes nothing, so show the person what it found, then call it again with dry_run false and the skills they picked. An import lands on, private to the person. skill-files-list and skill-files-content read the extra files a skill carries; load_skill returns the same files. - Knowledge Transcripts
knowledge_transcripts- The transcripts you sent Kenso from outside: by your transcript webhook URL, your email-in address or your Fathom connection, one per call. list shows each one's status (processing, ready, failed, removing) and the account Kenso matched it to. delete takes one back and deletes the facts, evidence and pending suggestions Ken made from it; the same delivery sent again stays out. - LinkedIn
linkedin - LinkedIn Connections
linkedin_connections- Manage your LinkedIn connections. Requests your seats receive: Kenso's spam and ICP triage, each seat's off, manual or autonomous accept setting, and accepting or skipping one request or many. Invitations your seats sent that are still pending: list them, and withdraw picked ones or all older than N days (queued and paced). The workspace's network: each seat's 1st-degree connections matched to Kenso Search and scored against the ICP, job changes, account suggestions, and promoting connections to accounts. Accept, skip or change a seat as its owner only when they ask: the change counts as the owner's own. The seats themselves (connect, reconnect, edit, remove) are the linkedin tool. - LinkedIn Enrich
linkedin_enrich- A LinkedIn seat's connections enrich job: Kenso sorts the seat's connections into buyers, partners and the rest, finds emails, and at the full level researches the buyers' accounts, best first, inside a hard credit cap. estimate first and get the user's yes on max_credits, then start; get and list read progress and spend, update raises the cap, cancel stops it. The connections themselves are linkedin_connections. people-suggestion-counts, people-accept-suggestions and people-undo-suggestions are Ken's suggested relationships for people in To sort: accept only on the user's request. - Lists
lists- Contact lists: a campaign's contact import lists (list_id; CSV, Kenso Search or campaign imports), plus the blocklist and a campaign's custom variables. Not people lists: saved lists of people or companies are the saved_lists tool, with their own ids, and delete here never takes a saved_list_id. - Lookups
lookups- The Kenso Chrome extension's reads for one tab: what a LinkedIn profile, company page or website is to the workspace (get: the verdict, owner, account, committee coverage, campaigns, reply and waiting drafts) and its toolbar badge (lookup-badges-get). Stored data only. Needs the extension feature. - Loopster
loopster- People and companies from Loopster, on the workspace's own Loopster API key: a search spends only that key's request limits, never Kenso credits. List the filters first, then search. Import the people you pick with contacts contact-imports-create, source loopster. Not Kenso Search. - Mail Messages
mail_messages- The caller's own Gmail or Outlook mail, read live: search it and read one message. Never Kenso's campaign replies (those are threads). - Market Stories
market_stories- Market news: the stories Kenso matched to the workspace from the day's headlines, each with an angle, tags and source links, and the topic profile they are matched against. list reads the open stories; get adds the suggested audience. profile-get reads the profile's industries, countries, vendors and keywords; profile-update replaces the lists sent. Not markets, which holds the writing rules of each market pack. - Markets
markets- Kenso's market packs: how to write cold email in each language and country (formality, salutations, sign-offs, style, banned phrases) and each country's cold email rules, a campaign's steps written in each language it enables, and the consent-first countries a campaign must acknowledge before launch. Not stock or financial markets. - MCP Servers
mcp_servers- The workspace's own third-party MCP servers (Linear, Notion, Atlassian, Airtable or any https server) whose tools Ken and the other agents use. list, get and presets-list read them; create (no sign-in or OAuth, never a token), update, delete and refresh-tools change them. Needs the custom_mcp flag. - Meeting Notes
meeting_notes- Notes and transcripts from meetings with target accounts (the Accounts lane). Attendees link to the account's people and stakeholders by email. Also scores a recorded call against the workspace's rubric (score-call, get-score), and reads or plans the follow-up email Ken drafts after a call (get-follow-up, draft-follow-up), and Ken's brief and call script before a call touch (touches-get-call-brief, touches-write-call-brief). - Meeting Results
meeting_results- Meetings Kenso booked for a pay-per-meeting workspace: list, proof, add, no-show, dispute, escalate, possible meetings - Meetings
meetings- Meetings on your calendar: account meetings your access covers, your own calendar events (events-* operations), each meeting's prep brief (get-brief), and what Kenso Notetaker recorded of a meeting: its transcript with speaker turns, times and the gaps a network drop left. list-sources shows where a meeting's notes came from (Kenso Notetaker, Fireflies, Fathom, Optiverse, Granola, a paste or an upload), the facts they produced and the new people on the call. Whether your own Fireflies and Fathom are connected; your own Optiverse and Granola are calendar optiverse-connection-get and granola-connection-get. Connecting stays in the Kenso app. - Members
members - Migrations
migrations- Import a workspace from Instantly, Smartlead, EmailBison, Salesforge, lemlist or Apollo (preview: Reply.io, Salesloft, Outreach): connect a key, discover, start a run, read the report. - Models
models- AI model settings and AI runs. How many contacts a flow would touch: get-eligibility, or ai-runs-create with dry_run=true. - Notetaker
notetaker- Kenso Notetaker for the caller. devices-list reads the caller's own Kenso desktop installs (platform, app version, last seen): a member with one seen in the last 14 days has the app, and no meeting bot joins their calls. The desktop app reports itself; there is no tool to write a device. call-types-* read and edit the workspace's call types: the notes template Ken picks for a call plus the recipe for the follow-up email after it. *-follow-up-draft read and work a meeting's follow-up as the Notes tab shows it; they never send, the meeting's owner approves in Kenso. - Onboarding
onboarding - Onboarding Builds
onboarding_builds - Opportunities
opportunities- Deals on your accounts: stage, amount, close date, owner and the people on each deal with their roles. One pipeline per workspace; stages are configurable. - Outbound Event Posts
outbound_event_posts- People going to an outbound event, found in public LinkedIn posts: check-posts looks again (once per event a day) and Kenso adds them in the background at a price per person, up to the event's spend limit. Read where it stands in outbound_events get (posts), the people with outbound_events attendees-list source=linkedin_post, and set the limit with outbound_events update (post_spend_limit_millicredits). - Outbound Events
outbound_events- Conferences and trade shows you work (Event outbound): each event and its attendee, exhibitor, speaker and sponsor list, every row matched to your target accounts by company domain, and the events Ken suggests to add. Not analytics events: those are analytics. - People
people- The real people in your workspace, on target accounts or on none (the Accounts lane): find, add, merge, export and find emails. Kenso Search's 280M people are the search tool. - Performance Deal
performance_deal- The workspace's done-for-you performance deal with Kenso: read its terms, offers and approved rate card, preview the card, add and edit offers (first-year ACV per company size band and the personas each targets) while the deal is draft or proposed, submit it for staff approval, and list its invoices and payments. - Permissions
permissions - Place Pulls
place_pulls- Bulk Google Maps place pulls: every place matching a query across whole countries or the world, read in the background, biggest cities first. estimate-place-pull is free: show the user its credits and coverage and get a yes before create-place-pull, which spends up to that (1 credit a page) and counts against the workspace's monthly bulk budget. One pull at a time: poll get-place-pull until status is not queued or running, then read list-place-pull-places (free). One area's places is search search-places. Needs search_places and places_bulk. - Prompts
prompts- A campaign's or segment's AI prompts (qualification, personalization, ...): list with campaign_id, alone; it needs no campaign read. - Qualify Runs
qualify_runs- Qualify every match of a Kenso Search people or companies search against a written fit definition, in the background (up to 5,000 rows, 0.05 credits a classified row): create (estimate_only=true first for the cost), get to poll, list-rows for the verdicts, cancel. For a short list of rows use models(operation="fit-classifications-create"). Needs the fit_classification feature. - Referrals
referrals - Replies
replies- threads-create starts a new email from a workspace inbox. reply-templates-* are saved reusable reply texts: reply-templates-delete removes a template, never a reply or a thread. Also signature, autonomous replies. The replies people sent (messages and threads) are the threads tool. - Roles
roles- The jobs a recruiting workspace hires for, each with a candidate pipeline by stage, and the extra roles a recruiting campaign also hires for. Extract reads a job link into a draft role. - Saved Lists
saved_lists- People lists: saved lists of people or companies (saved_list_id), the workspace's own, lists other workspaces shared with it, and Kenso's approved library. Build, copy, share and submit them; members and sources are operations here too. A receiving workspace reads and accepts an invite with invites-get and invites-accept. Not a campaign's contact import lists: those are the lists tool, with their own ids, and delete here never takes a list_id from it. - Saved Searches
saved_searches- Saved Kenso searches and their imports, plus company-data-get: any company's tech stack, brand and funding by its domain. - Scheduler
scheduler- Meeting types, Scheduler links and bookings for members' Scheduler pages: list meeting types and their open times, make a person's prefilled link or a single-use link, list or read bookings, mark a booking as a no-show, and reassign or cancel the upcoming bookings of a member who left. Needs the scheduler feature. - Search
search- Kenso Search: 280M people and companies, plus bulk pause, resume, restore and update of many workspace contacts (contacts-bulk-*). search-* and get-*-facets take one body object; its filter keys are in load_skill('ken-search'). When the request names the values, call search-people or search-companies with them directly: no facets, expand or get-filters first. When it asks which values exist (industry taxonomy names, with counts): get-people-facets. expand only suggests similar titles or industries with AI. Skip get-filters (the whole dropdown catalog, 20-50k tokens). A LinkedIn URL: search(operation="lookup-person", linked_in_url=...), or lookup-company. A company's tech stack, brand and funding by domain: saved_searches company-data-get. - Segments
segments- Campaign segments. preview counts the leads that match criteria and returns the filter catalog too, so call it directly. criteria uses the camelCase filter_criteria keys of create, such as titles, industries, seniorityLevels and leadQualityScore {min, max}. update replaces the whole filter_criteria: send every current key from get plus the change, as {"titles": ["CEO"], "profileCountries": ["United States"]}. process_filters assigns a segment's contacts from its saved filters: call it with segment_id, it reads the filters itself. Only a manual segment holds filter_criteria: update refuses it on an ai or ab_test segment, and an AI campaign's Default is ai. Narrow such a campaign with a new manual segment and process_filters; the leads it does not match stay in Default. - Sender Voice
sender_voice- Sender voice: Ken drafts in the voice of the member who owns the sending inbox or LinkedIn account. get and update are the caller's own switches and owner requests; the inbox and LinkedIn account owner operations read or set whose voice an inbox or account writes in. Settings and ids only. Needs the sender_voice flag. - Sending Providers
sending_providers- Send campaign mail through a provider's HTTP API (Resend, Agentmail, ...): connect a key, add sending addresses as inboxes, recheck the key and domains. The video-provider-connections-* operations connect the workspace's Sendspark, HeyGen or Vidyard account for campaign videos (early access). - Slack Alerts
slack_alerts- Proactive Slack alerts: Kenso posts in a channel on its own when a hot reply comes in, a meeting is booked, a campaign's bounce rate passes a threshold, a campaign stops sending or a domain is blacklisted. List, set up (create) or stop (delete) one. - Social
social- Records from LinkedIn, Facebook, Instagram, X, TikTok, YouTube and Crunchbase: lookup reads the links you have, search finds posts, jobs, people, ads and videos, resolve turns a link or a name into profiles, records lists what is stored for a contact, account or person (free). 0.15 credits a record on Kenso's key, 0 on the workspace's own key. A running result: get with its lookup_id or search_id until ready. - Studio Docs
studio_docs- Studio doc pages as files to forward: make a doc page from text you wrote (a report), and export a doc page as a Google Doc or Word file in the member's own drive. starters-get reads one Kenso library template (studio_templates starters-list finds them). template-slots-list lists a template's slots, the keys a studio.page@1 step's slots takes. Also: upload an image for one page's own layout (create-upload-url), import one from the member's Google Drive or OneDrive or an https URL for a page or template (create-image-upload), and the workspace brand kit (colors, fonts, logos) Studio pages, docs and templates style with: read it, change it, or suggest one from the website. - Studio Pages
studio_pages- Personalized Studio pages, one per template and account: fill runs, hand edits and natural links. A page's first link publishes it and charges 1 credit. - Studio Templates
studio_templates- Kenso Studio templates: reusable landing page and doc designs built from a bundle of files. Pull, edit and push the draft, validate, then publish a version. preview's sample is a bundle path such as samples/<name>.json. template_type is what it is for (reverse_demo, landing_page, audit, report, ...); template_format is page, doc or email. - Tags
tags - Threads
threads- A new email (not a reply) is not on this tool: replies(operation="threads-create", sender_inbox_id, to, subject, body, idempotency_key). Here: inbox threads (replies to campaigns). A reply in a thread: create-message with thread_id and body, no read needed first. Read, unread, archive, save and reminders: update or bulk-update with changes. create here only uploads an attachment. - Today
today- A member's queue for the day: touches waiting on them, tasks due today and setup rows, plus what they cleared today. Act on touch rows with account_touches. Also call tasks and the member's Call queue (call-tasks-*, call-queue-list), the member's logged calls and dialing (calls-*), and the call steps of a campaign or segment sequence (call-sequences-*, segment-call-sequences-*). - Tracking Links
tracking_links- A campaign's tracked links and their UTM parameters. tracking-links-list with campaign_id lists the links its emails use: domainName is the full destination URL, UTM tags (utm_source=...) included, and textValue the text the email shows; the copy places a link as {{tracking_link:ID}}. Add or change a link's UTM tags: tracking-links-update with changes {domainName: the URL with them}. The email copy itself is email_sequences get. video-* are campaign videos. - Triggers
triggers - Voice Notes
voice_notes- Preview a LinkedIn voice note step: Ken writes and speaks the note for up to 3 leads, free, 15 leads a day; and get a link to a voice note's audio (valid 1 hour). - Voices
voices- The voices a workspace can use for LinkedIn AI voice notes: list them, list the voices on the workspace's own ElevenLabs account, import one (only after the user confirms the rights) or remove an imported one. - Warm Paths
warm_paths- One started warm path: where each hop stands and the path as it was ranked (get). Rank, start and cancel paths with committee warm-paths-list and warm-paths-person and account_signals warm-paths-start and warm-paths-cancel. - Web
web- Web pages. search and the create-* jobs take every option inside body. scrape takes url, formats and only_main_content, and map takes url, limit and include_subdomains, at the top level or inside body; their other options go inside body: web(operation="scrape", url="https://...", formats=["markdown"]). - Webhooks
webhooks - Website
website- Your website's Kenso script (ken.js): the snippet, allowed domains, consent mode and visitor ID provider, the pages you tag as high intent with their points, and the human visits it saw. Also the outbound site: the rebuilt home page your outbound domains show, its fields, refresh, versions and preview. - Whatsapp
whatsapp- Connect and manage WhatsApp accounts (sessions through Unipile): status, daily caps, pauses and working hours, and the workspace's EU, EEA and UK setting. Also the workspace's WhatsApp message templates: text with {{variables}}, up to 6 images and an optional voice. - White Label
white_label - Workflow Builder
workflow_builder- Workflow builder: build writes a draft from a plain-words goal (start here to build a workflow), compile-condition turns one plain-words condition into a formula, and test runs the draft on one record with simulated actions. Nothing here goes live: after a passing test, call workflows(operation="publish"). Save to field targets (list and add custom fields) are here too. An AI step's with.knowledgePromptId links its text to a Knowledge prompt; it passes through untouched and the step runs its own text. - Workflow Runs
workflow_runs- Workflow runs: list runs, read one run's step trace, and recover runs. Retry a needs_attention run after fixing its setup problem; restart re-runs failed steps in place and keeps paid outputs; replay makes a new linked run. Bulk takes run ids or a filter (1,000 per call). Run-on-records starts a live workflow on up to 1,000 records: call it with estimate_only first and show the credits. A workflow's audit log (edits, publishes, run events) is activity with its workflow_id; account list is the workspace-wide log. - Workflows
workflows- Not on this tool: a workflow's audit log (edits, publishes, restores, runs) is workflow_runs(operation="activity", workflow_id=...); call only that, no get or versions-list before or beside it. Workflows: one trigger plus steps (find, enrich, qualify with AI, tag, notify) saved as a kenWorkflow definition with versions. Create a draft, validate it until valid is true (to check a saved workflow for problems, call validate with its workflow_id directly), then publish; update with draftVersion as base_version. unpublish turns a live workflow off. To build one from a plain-words request, call workflow_builder build with the request as the goal, ids included, before anything else. Compiling a condition and test runs are on workflow_builder; runs, their recovery and run-on-records are on workflow_runs. - Workspace
workspace- Workspaces. get, update and the tracking operations take workspace_id.