Choose a job to see its applications and compare available candidate information.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Read applications and candidate records to summarize the recruiting pipeline.
/oo Greenhouse: List applications for Greenhouse job [ID]. Read candidate details as needed and summarize application statuses with candidate and application IDs.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a Greenhouse Harvest API key with permissions for the required records.
Connect Greenhouse →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Greenhouse Harvest operations read job, candidate, and application records. Candidate notes can be added using a specified audit user.
List jobs, candidates, and applications, and retrieve their individual details.
List Greenhouse jobs with optional status, department, and timestamp filters.
Leina 
Wanta 
greenhouse.list_jobs Retrieve one Greenhouse job by ID.
greenhouse.get_job List Greenhouse candidates with optional job, email, candidate ID, and timestamp filters.
greenhouse.list_candidates Retrieve one Greenhouse candidate by ID.
greenhouse.get_candidate List Greenhouse applications with optional candidate, job, and status filters.
greenhouse.list_applications Retrieve one Greenhouse application by ID.
greenhouse.get_application Create a Greenhouse candidate activity feed note using an explicit On-Behalf-Of audit user.
greenhouse.add_candidate_note No matching tools.
List jobs and narrow them by status, department, or requisition ID.
No. A candidate profile and each application have separate IDs; use application records to compare hiring status.
Harvest keys require permissions for the relevant endpoints. Check the key’s access if job or candidate data is missing.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.