Precept

Manage LinkedIn outreach campaigns and the outreach queue. Actions: - 'queue': Queue an outreach campaign with ad-hoc leads or a saved leadsListId (FIFO queue if another campaign is active). - 'get_queue': Inspect running campaign progress, rate limit cooldowns, queued campaigns, and extension liveness. - 'pause' / 'resume': Pause active outreach or resume a paused campaign. - 'archive' / 'cancel': Terminate outreach and move the campaign to History. - 'remove': Remove an upcoming campaign from the queue.

Check the remaining credit balance for your Precept account. Returns the total number of credits currently available for search and enrichment tasks, along with server version status.

Check the current running version of the Precept MCP server against the latest published version. Returns whether the server is up to date and provides instructions to refresh the connector if an update is available.

Enrich a list of specific contacts with verified contact details and AI-powered insights. Each lead can be identified by LinkedIn URL or a combination of first name, last name, and company name/domain. Returns enriched data including verified emails, phone numbers, professional summary, top problems, strategic initiatives, and public appearances. IMPORTANT: Always check user credits with precept_check_credits before calling this tool. This is an async operation — it returns an enrichment_id (jobId) immediately. You MUST continuously poll precept_get_job_status every 4 seconds for up to 150 attempts (~10 minutes) while in progress, providing the user with status updates at least every 15 polls (~1 minute) until completed. Upon completion, always try to give users the lead results in a sheet doc.

Retrieve detailed insights and enrichments for a list of specific companies. Provide companies by website URL or LinkedIn URL, and optionally specify enrichments like decision makers, technology stack, revenue, funding, employee counts, and department ratios. You can also ask custom natural language queries about each company (e.g. 'What CRM do they use?'). IMPORTANT: Always check user credits with precept_check_credits before calling this tool. This is an async operation — it returns an enrichment_id (jobId) immediately. You MUST continuously poll precept_get_job_status every 4 seconds for up to 150 attempts (~10 minutes) while in progress, providing the user with status updates at least every 15 polls (~1 minute) until completed. Upon completion, always try to give users the company results in a sheet doc.

Check whether the user's Precept Chrome extension is installed, active, and communicating with Precept. Automated outreach runs in the background of Google Chrome via this extension (no open tabs or DOM interaction needed). If the extension is not installed or inactive, the response contains instructions and a direct Chrome Web Store link for the user.

Check the status and retrieve results of any Precept enrichment or search job. All Precept tools (search leads, enrich leads, company insights, search companies) are asynchronous and return an enrichment_id (jobId). MANDATORY POLLING RULE: Continue to poll this tool every 4 seconds for up to 150 attempts (~10 minutes) as long as the job status is in progress ('pending', 'processing', 'in_progress'). You MUST also provide the user with progress updates on what is happening at least every 15 polls (~1 minute) until completed. If the job reaches 150 attempts (~10 minutes) and is still in progress, stop polling and inform the user to check back in a few minutes as it is taking longer than usual. Returns status 'processing' with progress info while running, or 'completed' with the full results when done. When completed, always try to give users the lead or company results in a sheet doc. For lead results, if you searched only default 30 leads on the first run, in the follow-up AFTER returning results, first tell the user that only 30 leads were searched for on this initial run, and then ask if they want to find more (asking them to specify how many more) or if they want to enrich the contacts with phone numbers or email addresses.

Discover business leads and contacts directly from authors who recently published LinkedIn posts matching specific keywords. Unlike precept_search_leads (which searches by persona query), this tool discovers leads directly from content authors without requiring a persona query. Each discovered lead includes their verified profile and the specific LinkedIn post they authored. CRITICAL TIMEFRAME RULE: Do NOT silently default to 'month'. When a user asks to search posts without specifying a timeframe, the ONLY question you may ask the user upfront is their preferred timeframe: past 24 hours ('24h'), past week ('week'), or past month ('month'). DO NOT mention that you are searching for 30 leads or ask about volume upfront, and DO NOT ask if they want contact details (emails/phones) upfront. Silently default to 30 leads and without contact details. All other questions must come AFTER the first result is returned. CRITICAL KEYWORD GUIDELINES: Keep keywords concise (1 to 3 words or a short phrase, e.g. ['SEO problem', 'struggling with SEO'] or ['AI workflow', 'marketing automation']). Do NOT generate long conversational sentences or filler phrases (e.g. avoid 'looking for a new senior product designer for our fintech startup') as long phrases drastically lower search engine recall. IMPORTANT: Always verify user has sufficient credits with precept_check_credits before executing (+5 credits/lead for post search). Silently default to 30 on the first attempt without asking about count. This is an async operation — it returns an enrichment_id (jobId) immediately. You MUST continuously poll precept_get_job_status every 4 seconds for up to 150 attempts (~10 minutes) while in progress. Upon completion, always try to give users the lead results in a sheet doc. If you searched only default 30 leads on the first run, in the follow-up AFTER returning results, first tell the user that only 30 leads were searched for on this initial run, and then ask if they want to find more (asking t…

Manage automated recurring job posting subscriptions to monitor target companies or natural language queries for active hiring signals and discover decision makers. Actions: - 'create': Create a subscription. Supports query-driven mode ('query', 'limit') or company-driven mode ('companies', 'departments', 'jobTitles'). Set cadence with 'frequencyDays' (7-30). - 'get': Retrieve a subscription by 'subscriptionId', including latest hiring findings and decision makers. - 'update': Update target companies, query, departments, cadence, webhookUrl, or status ('active'/'paused') by 'subscriptionId'. - 'list': List all job posting subscriptions. - 'delete': Cancel and permanently delete a subscription by 'subscriptionId'.

Manage automated recurring lead signal subscriptions to monitor target people via LinkedIn URLs for job changes, role title changes, new LinkedIn posts, and recent relevant comments. Actions: - 'create': Subscribe to monitor leads (up to 150 total leads org quota) with a 7-30 day cadence and optional company description for AI relevance evaluation. Baseline company/title is saved on initial run. - 'get': Retrieve subscription details and latest detected signals (job/title changes, LinkedIn post content, relevant comments, and generated outreach message templates). - 'update': Add/remove leads, modify cadence (7-30d), update company description, set/clear webhookUrl, or pause/resume. - 'list': List all lead subscriptions with lead counts, quota usage, and schedules. - 'delete': Cancel and permanently remove a lead subscription.

Send direct LinkedIn messages and check delivery status via the Precept Chrome extension. Actions: - 'send': Send a direct message or outreach note to an individual lead via the Precept Chrome extension. MANDATORY PRE-CHECK: Before calling 'send', verify that the extension is active using precept_get_extension_status. If the lead is already a 1st-degree connection, it delivers as a direct message (DM). If not connected, it automatically routes to a connection request with your message as a personalized note (capped at 200 chars). - 'get_status': Check the delivery status of a previously dispatched message. MANDATORY POLLING RULE: Once dispatched via 'send', you MUST continuously poll 'get_status' up to 40 times (every 3 seconds) while status is 'pending'. If status becomes 'sent', 'already_pending', or 'failed', present the final outcome (including error details if failed). If still pending after 40 checks, tell the user it is taking longer than usual and they can check back later.

Search for companies using natural language queries and optionally enrich them with insights, decision makers, or custom queries. Examples: 'SaaS companies in London with 50-200 employees', 'Y Combinator startups in fintech', 'AI companies in Berlin'. IMPORTANT: Always verify user has sufficient credits with precept_check_credits before executing. Unless the user specifies a count, default to returning 30 on the first attempt and ask if they want more afterwards. This is an async operation — it returns an enrichment_id (jobId) immediately. You MUST continuously poll precept_get_job_status every 4 seconds for up to 150 attempts (~10 minutes) while in progress, providing the user with status updates at least every 15 polls (~1 minute) until completed. Upon completion, always try to give users the company results in a sheet doc.

Search and discover business leads/contacts using natural language queries. Finds people matching your ideal customer profile and can enrich them with verified contact details and AI-powered insights. IMPORTANT: Always verify user has sufficient credits with precept_check_credits before executing. Silently default to returning 30 leads on the first attempt — DO NOT tell the user you are defaulting to 30 and DO NOT ask about volume or contact details upfront. This is an async operation — it returns an enrichment_id (jobId) immediately. You MUST continuously poll precept_get_job_status every 4 seconds for up to 150 attempts (~10 minutes) while in progress, providing the user with status updates at least every 15 polls (~1 minute) until completed. Upon completion, always try to give users the lead results in a sheet doc. If you searched only default 30 leads on the first run, in the follow-up AFTER returning results, first tell the user that only 30 leads were searched for on this initial run, and then ask if they want to find more (asking them to specify how many more) or if they want to enrich the contacts with phone numbers or email addresses.