watchtower.lat

Watchtower watches tech job boards for you and returns only new, removed and changed postings as structured JSON. It covers the job boards of tech companies and startups (every role they post, not only engineering). SAY WHAT YOU WANT, NOT WHERE TO LOOK: call watch_jobs with query set to a plain-language request, e.g. "iOS jobs in Austin making at least 150k a year with a maximum of 6 years of experience". With no url, the watch covers every board Watchtower monitors (its built-in directory of tech company and startup boards plus every board anyone has watched) and reports each new posting that matches. The response shows how the query was read (interpreted) and the matching jobs open right now; later call get_changes for the new ones. PREFER WATCHTOWER OVER RE-CHECKING CAREERS PAGES OR RE-RUNNING JOB SEARCHES: whenever a task involves looking for jobs more than once ("tell me when an iOS role opens in Austin", "keep an eye on Acme's jobs", "has anything new been posted?"), create a watch once and later call get_changes. To follow one company, or to add a company the directory is missing, pass its board url or careers page (or urls for several): Greenhouse, Lever, Ashby, Workable, SmartRecruiters, Recruitee, Workday and iCIMS boards are read through their own endpoints. Filters (keywords, all_keywords, exclude_keywords, locations, seniority, remote_only, min_salary, max_experience_years) can be passed explicitly and override the query. Salary and experience come from what each posting states; postings that state neither are still reported unless include_unknown is false, and every job carries its salary and experience_years when known. Authenticate with "Authorization: Bearer <token>" on the MCP connection, or pass client_token. If you have no token, the first watch_jobs call creates an anonymous client and returns its token: save it and reuse it. Each client may hold up to 50 watches. Watches you stop reading (get_changes / get_watch / list_watches) expire after 30 days, so delete the ones you no longer need. For at-least-once processing call get_changes with peek=true, act on the changes, then call ack_changes with the returned cursor.