Pipeline tools

The stage values, in order: WISHLIST · APPLIED · SCREEN · INTERVIEW · FINAL · OFFER · ACCEPTED · REJECTED · WITHDRAWN · GHOSTED The activity types: NOTE · STAGE_CHANGE · EMAIL_SENT · EMAIL_RECEIVED · CALL · INTERVIEW · FOLLOW_UP · APPLIED · OFFER · REJECTION · REFERRAL · OUTREACH Three tools answer “what is due”, and the difference matters: list_follow_ups is what is already overdue, list_schedule is a whole window of dated work merged together, and list_tasks is to-dos regardless of date. How the pipeline works →

​

pipeline_stats

Pipeline stats Counts by stage, active applications, applications sent this week, interviews, offers, open tasks, follow-ups due and response rate. Start here for any ‘how is my search going’ question. No arguments.

​

list_applications

List applications List job applications. By default the closed ones (accepted, rejected, withdrawn, ghosted) are excluded. Every row carries daysInStage — how long it has sat where it is, measured from the last stage change rather than the last edit — which is the field to sort on when someone asks what has gone quiet or what needs chasing.

​

get_application

Get an application Full detail for one application including the job description, the complete activity timeline, contacts and tasks.

​

capture_job_posting

Capture a job posting from its URL The FIRST tool to call when someone shares a link to a job posting. Fetches the page server-side, reads the structured posting data most job boards publish, and creates the application in one move: company matched or created (with its own website when the posting names one, which puts their logo on the pipeline), role title, full description, location, compensation and source all filled, starting on the wishlist. Returns captured true with the new application and its id. When the page doesn’t state the employer or the role readably, returns captured false plus whatever WAS parsed and creates NOTHING — in that case show the person what was found, ask for the missing pieces, and use create_application. Never guess an employer’s name from a URL. If they applied already, follow with move_application_stage. Overwrites or deletes. Reaches outside this instance.

​

list_application_sources

List the source channels on file The source labels this person already uses (‘LinkedIn’, ‘Referral from Dana’, …), most-used first, followed by the standard starters. Call it before writing sources on create_application or update_application so you reuse their exact spellings instead of minting near-duplicates — it covers every application including closed ones, which list_applications hides by default. Read-only. No arguments.

​

create_application

Create an application Track a new job. Paste the full posting into jobDescription — it is what you will tailor the resume against later. The company is created automatically if it does not exist. Pass companyWebsite when you know it — it is what makes the company’s logo appear in the pipeline, and it costs nothing to include. A job link and description are OPTIONAL: an application that started as a LinkedIn message with no listing is still an application — track it with just company and roleTitle, put ‘Cold outreach’ in sources, and attach the person messaged with create_contact. Overwrites or deletes.

​

update_application

Update an application Update fields on an application. Changing stage here also writes a timeline entry and resets the follow-up date. sources REPLACES the whole list — read the current one from get_application, add or remove, and pass the full list back. Overwrites or deletes.

​

move_applications_stage

Move several applications to one stage Move a batch of applications to the same stage — the tool for ‘close out everything I never heard back from’ or ‘mark these four as applied’. Each one gets its own timeline entry and follow-up date, exactly as if it had been moved on its own, so the funnel history stays intact. Ids that no longer exist are skipped rather than failing the batch; the result lists what moved and what was skipped. Read the ids from list_applications first, and for silence use GHOSTED rather than REJECTED. Overwrites or deletes.

​

move_application_stage

Move an application to a new stage Advance or close an application. Automatically logs the change to the timeline and schedules the next follow-up. On the four endings: REJECTED is for when they said no, WITHDRAWN for when the user pulled out, ACCEPTED for a signed offer, and GHOSTED for the far more common ending where nobody ever replied. Use GHOSTED rather than REJECTED when there was no answer — the funnel counts a rejection as a decision against the user and a ghosting as a non-response, and the advice that falls out of those is different. Overwrites or deletes.

​

delete_application

Delete an application Permanently delete an application and its timeline. Overwrites or deletes.

​

log_activity

Log activity on an application or a contact Append to a timeline. Pass applicationId for things that happened on an application — a recruiter call about the role, an interview, a note to self. Pass contactId for things that happened with a PERSON — a coffee, a call, a reply — and it becomes their history: the contact’s page shows it and their ‘last touched’ date moves. Exactly one of the two, never both. When someone mentions talking to a person they know, this with contactId is how it gets remembered. Type OUTREACH is for messages the user sent first — a LinkedIn DM to a hiring manager, a cold email — which is how many applications actually start.

​

list_activities

List recent activity Recent timeline entries across the whole search, or for one application. Good for ‘what happened this week’.

​

list_follow_ups

List follow-ups that are due The ‘who do I need to chase today’ tool. Returns two lists: applications whose follow-up date has arrived or passed, and contacts whose ping date has — the people you meant to get back in touch with. Both are due work; plan a day from the pair.

​

diagnose_search

Diagnose the job search Works out what is actually going wrong with the search, rather than reporting counts. Returns a one-sentence verdict naming which step of the funnel is losing people — no responses at all is a resume or targeting problem, responses that die at the phone screen is a story problem, interviews that do not convert is something else again — plus per-step conversion, median days spent in each stage, weekly volume for the last six weeks, applications that have gone quiet, and the response rate of each resume so you can see which one is working. Progress is measured by the furthest stage an application ever reached, so a rejection after a final round counts as having got that far. Reach for this before giving advice about a search: it is the difference between ‘send more applications’ and ‘stop sending, the resume is the problem’. Says so plainly when there is not enough data yet. Read-only. No arguments.

​

share_pipeline

Get a read-only link to the pipeline Mint a link that shows this person’s pipeline to anyone holding it, without a login — for a friend, a coach or a former manager who is helping review the search. Returns publicUrl, which is the whole point: hand it straight to the user. Calling it twice returns the same link rather than a second one. What a viewer sees is deliberately narrow: company, role, stage, location, how long each has been sitting and when a follow-up is due. They do NOT see notes, job descriptions, salary, contacts or the activity timeline — say so if someone asks what will be visible, because a share link is consent to show a search, not to publish the people in it. Set include_closed to show finished applications too.

​

unshare_pipeline

Revoke the pipeline link Stop sharing the pipeline. This DESTROYS the address rather than pausing it — anyone holding the old link gets nothing, and sharing again later mints a completely different URL. That is deliberate: the reason to revoke is usually that a link reached someone it should not have, and a pause that can be undone does not fix that. Overwrites or deletes. No arguments.

​

get_pipeline_share

Check whether the pipeline is shared Whether a read-only pipeline link currently exists, what it shows, and when it was last opened. Returns null when nothing is shared, and publicUrl when something is. Use it before minting a link so you can tell someone they already have one, and to answer ‘has anyone actually looked at it’. No arguments.

​

list_saved_views

List saved pipeline views The cuts of the pipeline this person has named and kept — ‘Chasing’, ‘Dream jobs’, ‘Gone quiet’. Each one returns a name and a query string like “view=list&f=SCREEN,INTERVIEW&sort=waiting”. Call this when someone refers to a view by name, then use the query to work out what they mean: f is a comma-separated list of stages, sort and dir order the table, q is a search. Reading a view tells you what they consider one job; it is a good place to look before asking what they want reviewed. No arguments.

​

save_view

Save a pipeline view under a name Name a cut of the pipeline so it can be reopened in one click. The query is the pipeline URL’s own parameters without the leading ’?’: view (board | list | calendar), f (comma-separated stages, or ‘overdue’ / ‘closed’), sort, dir, q (search), and month (YYYY-MM, which the calendar view uses). Example: name ‘Gone quiet’, query ‘view=list&f=APPLIED,SCREEN&sort=waiting&dir=desc’. Saving under a name that already exists REPLACES that view rather than creating a second one, which is how you edit one. Anything outside those parameters is dropped. Overwrites or deletes.

​

delete_saved_view

Delete a saved view Remove a saved pipeline view. Only the view goes — nothing about the applications it was showing is touched. Get the id from list_saved_views. Overwrites or deletes.

​

list_schedule

List everything dated in a window Everything with a date attached between two dates, merged into one list sorted earliest first: follow-ups that come due, tasks with a due date, and activity already logged (calls, interviews, emails, stage changes). This is the tool for ‘what does my week look like’, ‘what happened last month’ or ‘what is coming up’ — anything where the question is about a period of time rather than about one application. Each entry says its kind (FOLLOW_UP, TASK or ACTIVITY), the date, a title, the company and the applicationId, so you can call get_application for the full picture. Reach for list_follow_ups instead when you only want what is already overdue, and list_tasks when the date does not matter. Read-only; it saves nothing.

​

list_tasks

List tasks To-dos, optionally attached to an application.

​

create_task

Create a task Add a to-do, optionally attached to an application and with a due date.

​

complete_task

Complete or reopen a task Mark a task done, or reopen it with done: false. Overwrites or deletes.