Tools
156 available tools
Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.
156 tools found.
Activate user
Tool name:
activate_userReactivate a previously deactivated user so they can sign in to Greenhouse and be assigned to new jobs again.
Add candidate note
Tool name:
add_candidate_noteCreate a candidate note, log an email, or record an activity-feed entry on a candidate.
Bulk activate users
Tool name:
bulk_activate_usersReactivate up to the bulk-endpoint cap of users in a single request.
Bulk create blocked spam sources
Tool name:
bulk_create_blocked_spam_sourcesAdds multiple blocked spam sources in a single request, typically used to sync the blocklist from an external security tool.
Bulk create candidates
Tool name:
bulk_create_candidatesAsynchronously create many candidate profiles in a single call, typically for HRIS sync workflows that create a batch of candidates at once.
Bulk create custom field options
Tool name:
bulk_create_custom_field_optionsAsynchronously add many options at once, typically for HRIS sync workflows that replace or extend a dropdown's option set in a single pass.
Bulk create jobs
Tool name:
bulk_create_jobsAsynchronously create many jobs in a single call, typically for HRIS sync workflows that open a batch of requisitions at once.
Bulk create openings
Tool name:
bulk_create_openingsAsynchronously add many openings across one or more jobs in a single call, typically for HRIS sync workflows that open or extend headcount on a batch of requisitions.
Bulk create users
Tool name:
bulk_create_usersCreate up to the bulk-endpoint cap of users in a single request.
Bulk deactivate users
Tool name:
bulk_deactivate_usersDeactivate up to the bulk-endpoint cap of users in a single request.
Bulk revoke permissions users
Tool name:
bulk_revoke_permissions_usersDemote up to the bulk-endpoint cap of site admins to Basic users in a single request.
Bulk update blocked spam sources
Tool name:
bulk_update_blocked_spam_sourcesUpdates the note on multiple blocked spam sources in a single request.
Bulk update custom field options
Tool name:
bulk_update_custom_field_optionsAsynchronously edit the label, sort order, or external id of many options in one call — most often used to reorder a dropdown after an upstream HRIS reshuffle or to rename options en masse.
Bulk update departments
Tool name:
bulk_update_departmentsAsynchronously update many departments in a single request.
Bulk update offices
Tool name:
bulk_update_officesUpdate up to the bulk-endpoint cap of offices in a single request.
Bulk update openings
Tool name:
bulk_update_openingsAsynchronously patch many openings in a single call, commonly for HRIS integrations that close batches of headcount with status: "closed" and close_reason_id, or reconcile partner opening_id values…
Bulk update users
Tool name:
bulk_update_usersUpdate up to the bulk-endpoint cap of users in a single request.
Convert prospect to candidate
Tool name:
convert_prospect_to_candidatePromote a prospect application to a candidate application on a specific job.
Create application
Tool name:
create_applicationCreate a new application for an existing candidate.
Create applied candidate tag
Tool name:
create_applied_candidate_tagApply an existing tag to a candidate.
Create approval flow
Tool name:
create_approval_flowCreate a multi-step approval flow on a job (and optionally a specific offer), seeded with the supplied approver groups.
Create attachment
Tool name:
create_attachmentAttach a file to an existing application.
Create blocked spam source
Tool name:
create_blocked_spam_sourceAdds a new IP address, CIDR range, email address, or email domain to the organization's spam blocklist.
Create candidate
Tool name:
create_candidateCreate a new candidate profile in your organization.
Create candidate education
Tool name:
create_candidate_educationAdd a new education entry to a candidate's profile.
Create candidate employment
Tool name:
create_candidate_employmentAdd a new work history entry to a candidate's profile.
Create candidate tag
Tool name:
create_candidate_tagAdd a new tag to your organization's candidate-tag dictionary.
Create custom field
Tool name:
create_custom_fieldAdd a new custom field to your organization's dictionary.
Create custom field department
Tool name:
create_custom_field_departmentRestrict a custom field's visibility to one additional department.
Create custom field office
Tool name:
create_custom_field_officeRestrict a custom field's visibility to one additional office.
Create custom field option
Tool name:
create_custom_field_optionAdd a new selectable value to a single_select or multi_select custom field.
Create department
Tool name:
create_departmentCreate a department in the caller's organization.
Create future job permission
Tool name:
create_future_job_permissionGrant a user a Job Admin role on future jobs matching an optional department and/or office scope.
Create interview
Tool name:
create_interviewSchedule an interview against a candidate's application at a specific slot on the job's interview plan.
Create job
Tool name:
create_jobCreate a new job from an existing template.
Create job hiring manager
Tool name:
create_job_hiring_managerAssign a user as a hiring manager on a job.
Create job note
Tool name:
create_job_noteCreate a free-form note attached to a job.
Create job owner
Tool name:
create_job_ownerAdd a user to a job's hiring team as a recruiter, sourcer, or coordinator.
Create job post
Tool name:
create_job_postCreate a new job post by duplicating an existing one.
Create job post location
Tool name:
create_job_post_locationAttach a location to an existing job_post.
Create offer
Tool name:
create_offerCreate a new offer on an existing application.
Create office
Tool name:
create_officeCreate a new office for the organization.
Create opening
Tool name:
create_openingAdd a new headcount slot to an existing job.
Create scorecard
Tool name:
create_scorecardCreate a scorecard for a given interview kit on a given application.
Create scorecard candidate attribute
Tool name:
create_scorecard_candidate_attributeDeprecated — where available, prefer the nested candidate_attributes array on POST/PATCH /v3/scorecards, which writes ratings atomically with the scorecard.
Create scorecard question answer
Tool name:
create_scorecard_question_answerDeprecated — where available, prefer the nested question_answers array on POST/PATCH /v3/scorecards, which writes answers atomically with the scorecard and supports every answer type including…
Create scorecard question answer option
Tool name:
create_scorecard_question_answer_optionDeprecated — where available, prefer the nested question_answers array on POST/PATCH /v3/scorecards, where a select question's value replaces the whole selection as a set (the only way to remove a…
Create user
Tool name:
create_userCreate a new Greenhouse user in your organization.
Create user email
Tool name:
create_user_emailAttach an additional email address to a Greenhouse user — the V3 replacement for V1 POST /users/{id}/email_addresses.
Create user job permission
Tool name:
create_user_job_permissionGrant a user a Job Admin role on a single job.
Deactivate user
Tool name:
deactivate_userDeactivate a Greenhouse user.
Get bulk request
Tool name:
get_bulk_requestRetrieve a single bulk request, including the per-row success and failure result files.
Get job
Tool name:
get_jobJobs are the open requisitions and hiring plans your organization is recruiting against.
Get rejection reason
Tool name:
get_rejection_reasonRetrieve a single rejection reason by id.
Hire application
Tool name:
hire_applicationMark an application as hired and close out the matching opening on the job.
List AI opt out statuses
Tool name:
list_ai_opt_out_statusesA candidate's decision to opt out of AI-assisted review (Talent Matching) for a specific job.
List application stages
Tool name:
list_application_stagesApplication stages are the rows that make up a candidate's stage history on an application — one row per interview stage the application has occupied, with entered_at and exited_at timestamps.
List applications
Tool name:
list_applicationsList applications from Greenhouse.
List applied candidate tags
Tool name:
list_applied_candidate_tagsApplied candidate tags are the join rows between candidates and the organization's candidate-tag dictionary — one row per (candidate, tag) pair.
List approval flows
Tool name:
list_approval_flowsApproval flows are the multi-step approval definitions attached to a job or to a candidate's offer.
List approver groups
Tool name:
list_approver_groupsApprover groups are the ordered tiers of approvers inside a single approval flow on a job or offer.
List approvers
Tool name:
list_approversApprovers are the individual users assigned to approve a job, offer, or other approvable resource.
List attachments
Tool name:
list_attachmentsAttachments are files associated with an application — resumes, cover letters, take-home tests, offer documents, e-signed agreements, and other supporting documents.
List blocked spam sources
Tool name:
list_blocked_spam_sourcesLists the IP addresses, CIDR ranges, email addresses, and email domains the organization has blocked from submitting applications.
List bulk requests
Tool name:
list_bulk_requestsBulk requests track the asynchronous bulk operations submitted to Harvest V3.
List candidate attribute types
Tool name:
list_candidate_attribute_typesCandidate attribute types are the structured attribute dictionary on a job — the per-job catalogue of evaluable traits (e.g. JavaScript, Leadership, Years of experience) that get rated on scorecards…
List candidate educations
Tool name:
list_candidate_educationsCandidate educations are the school/degree/discipline entries on a candidate's profile — one row per education entry.
List candidate employments
Tool name:
list_candidate_employmentsCandidate employments are the work history entries on a candidate's profile — one row per employer/title the candidate has held.
List candidate tags
Tool name:
list_candidate_tagsCandidate tags are the org-wide library of tag names available to apply to candidates (e.g. engineering, referral, 2026-grad).
List candidates
Tool name:
list_candidatesList candidates from Greenhouse.
List close reasons
Tool name:
list_close_reasonsClose reasons are the organization-defined dictionary of outcomes recorded when an opening is closed (e.g. Hire - New Headcount, Hire - Backfill, On Hold, Not Filling).
List custom field departments
Tool name:
list_custom_field_departmentsA custom_field_department restricts a custom field's visibility to a single department, so the field only appears on jobs, offers, or candidates whose department matches.
List custom field offices
Tool name:
list_custom_field_officesA custom_field_office restricts a custom field's visibility to a single office, so the field only appears on jobs, openings, or offers whose office matches.
List custom field options
Tool name:
list_custom_field_optionsCustom field options are the selectable values on a single_select or multi_select custom field — each row belongs to exactly one custom field via custom_field_id.
List custom fields
Tool name:
list_custom_fieldsCustom fields are the org-defined dictionary of structured data your organization layers onto core resources — jobs, offers, openings, candidates, applications, and users.
List default interviewers
Tool name:
list_default_interviewersDefault interviewers are the users pre-selected as the interview panel for a specific stage on a job.
List demographic answer options
Tool name:
list_demographic_answer_optionsDemographic answer options are the selectable choices on a demographic_question.
List demographic answers
Tool name:
list_demographic_answersDemographic answers are individual applicant submissions to the organization's voluntary demographic questions on a job post — distinct from the federally-mandated EEOC questionnaire, which has its…
List demographic question sets
Tool name:
list_demographic_question_setsDemographic question sets are named groupings of demographic_questions an organization attaches to a job post or candidate survey to collect self-reported applicant demographic data (e.g. for DE&I…
List demographic questions
Tool name:
list_demographic_questionsDemographic questions are the voluntary self-identification prompts applicants see on job posts and candidate surveys (separate from the EEOC questionnaire, which carries its own legally-mandated…
List departments
Tool name:
list_departmentsDepartments are the organizational units jobs are assigned to (e.g. Engineering, Marketing).
List eeoc
Tool name:
list_eeocEEOC responses capture a candidate's voluntary self-identification of race, gender, veteran status, and disability status, collected via the federally-approved Equal Employment Opportunity Commission…
List email templates
Tool name:
list_email_templatesEmail templates are reusable subject/body pairs your organization uses to communicate with candidates, prospects, and the hiring team.
List focus candidate attributes
Tool name:
list_focus_candidate_attributesFocus candidate attributes are the subset of a job's job_candidate_attributes that an individual interview kit elevates as focus areas — the attributes Greenhouse highlights at the top of the…
List future job permissions
Tool name:
list_future_job_permissionsFuture job permissions grant a user a Job Admin role on jobs that don't exist yet — when a new job is created in the matching department and/or office, the permission automatically assigns the user…
List interview kits
Tool name:
list_interview_kitsInterview kits are the per-job, per-slot evaluation packets interviewers see when conducting an interview — the instructions, exercises, scorecard questions, and focus attributes attached to one slot…
List interview media
Tool name:
list_interview_mediaInterview media contains recordings and transcripts created by Greenhouse AI notetaking.
List interviewer tags
Tool name:
list_interviewer_tagsInterviewer tags are organization-defined labels assigned to interviewer users, such as "Bar Raiser," "Diversity Trained," or "Senior." They are surfaced as Interviewer Groups in the Greenhouse UI…
List interviewers
Tool name:
list_interviewersInterviewers are the panel members on actual scheduled interviews — each row pairs one interview with one user (or, for external attendees, one email address).
List interviews
Tool name:
list_interviewsInterviews are scheduled interview events on a candidate's application — each row pairs an application with a slot on the job's interview plan (the job_interview) and carries the start/end time,…
List job board custom locations
Tool name:
list_job_board_custom_locationsJob board custom locations are the curated list of location strings a site admin maintains for posting jobs to a given job board.
List job boards
Tool name:
list_job_boardsA job board is a destination an organization publishes job posts to — either the organization's single internal board (visible only to signed-in employees) or one of its external boards (public…
List job candidate attributes
Tool name:
list_job_candidate_attributesJob candidate attributes are the per-job instances of a job's candidate_attribute_types — one row for each evaluable trait (e.g. JavaScript, Leadership) configured on a specific job.
List job hiring managers
Tool name:
list_job_hiring_managersJob hiring managers are users designated as hiring managers on a job — typically the subject-matter expert for the role who reviews candidates in the Hiring Manager Review stage and receives…
List job interviews
Tool name:
list_job_interviewsJob interviews are the interview slots configured on a job's interview plan — the template definitions that say, for example, "this job's Onsite stage has a 30-minute recruiter chat, a 45-minute…
List job notes
Tool name:
list_job_notesJob notes are free-form, organization-internal notes attached to a job (the requisition).
List job owners
Tool name:
list_job_ownersJob owners are the recruiters, sourcers, and coordinators on a job's hiring team — the users who own sourcing, recruiting, and scheduling work for the role.
List job post locations
Tool name:
list_job_post_locationsJob post locations are the join rows that attach one or more locations to a job_post — a multi-location posting (e.g. San Francisco, Remote (US), New York on a single role) has one row per location.
List job post searchable locations
Tool name:
list_job_post_searchable_locationsSearchable locations are the individual geographic locations attached to a job post — one row per location, each with a formatted display string plus its component city, region (state/province),…
List job posts
Tool name:
list_job_postsJob posts are the candidate-facing listings of a job.
List job stages
Tool name:
list_job_stagesInterview stages are the steps of a job's interview plan — for example Application Review, Phone Screen, Onsite, and Offer.
List jobs
Tool name:
list_jobsList jobs from Greenhouse.
List notes
Tool name:
list_notesEach note is anchored to a candidate and optionally to a specific application.
List offers
Tool name:
list_offersOffers are the formal job offers extended to a candidate's application.
List offices
Tool name:
list_officesOffices are the organization's recruiting locations (e.g. San Francisco, New York, Remote (US)) and the foundational scoping unit for jobs, candidates, custom-field visibility, and pay-range display.
List openings
Tool name:
list_openingsOpenings are the individual headcount slots beneath a job — one opening per seat you intend to hire for.
List pay input ranges
Tool name:
list_pay_input_rangesPay input ranges are the per-job-post minimum and maximum values for a pay component (e.g. base salary, bonus) referenced by a pay transparency rule.
List pay inputs
Tool name:
list_pay_inputsPay inputs are the individual compensation components (e.g. Base Salary, Sign-on Bonus, Equity) that make up a Greenhouse pay transparency rule.
List prospect details
Tool name:
list_prospect_detailsA prospect detail is the per-prospect record that captures where a candidate sits in the CRM: which prospect pool and stage they currently occupy, who owns them, and the department/office they are…
List prospect pool stages
Tool name:
list_prospect_pool_stagesProspect pool stages are the smaller buckets inside a prospect pool that recruiters use to track where each passive prospect sits in their nurture process — for example Not Reviewed, In Discussion,…
List prospect pools
Tool name:
list_prospect_poolsA prospect pool is an organization-defined collection of prospects (candidates not yet attached to a specific job), typically used to manage talent communities and sourcing pipelines.
List referrers
Tool name:
list_referrersReferrers are the people credited with bringing a candidate into the pipeline — typically employees making referrals, but also agency recruiters, LinkedIn recruiters, or any other party captured…
List rejection details
Tool name:
list_rejection_detailsRejection details are the per-application rejection records — one row per rejected application, capturing who rejected it, when, why (the rejection reason), the linked rejection note, and any answers…
List rejection reasons
Tool name:
list_rejection_reasonsRejection reasons are the organization-defined dictionary of outcomes recorded when an application is rejected (e.g. Not a cultural fit, Lacking skill(s)/qualification(s), Wasn't interested, Didn't…
List scorecard candidate attributes
Tool name:
list_scorecard_candidate_attributesScorecard candidate attributes are the per-scorecard ratings an interviewer captured on each focus attribute — what they thought of this candidate on each attribute on this scorecard.
List scorecard question answer options
Tool name:
list_scorecard_question_answer_optionsScorecard question answer options are the join rows between a scorecard question answer and the option(s) selected for it — one row per (scorecard_question_answer_id, scorecard_question_option_id)…
List scorecard question answers
Tool name:
list_scorecard_question_answersA scorecard question answer is one interviewer's response to a single question on a scorecard.
List scorecard question candidate attributes
Tool name:
list_scorecard_question_candidate_attributesScorecard question candidate attributes are the join that tells an interviewer which focus attributes a given scorecard question is asking them to assess.
List scorecard question options
Tool name:
list_scorecard_question_optionsScorecard question options are the multiple-choice values shown to interviewers for single_select and multi_select scorecard_questions.
List scorecard questions
Tool name:
list_scorecard_questionsScorecard questions are the prompts configured on an interview_kit that interviewers answer when submitting a scorecard.
List scorecards
Tool name:
list_scorecardsScorecards are the per-interview evaluations that interviewers fill out — overall recommendation, key takeaways, private and public notes, and ratings on the interview kit's focus attributes.
List sources
Tool name:
list_sourcesSources are the organization-defined dictionary of channels through which candidates enter the pipeline — job boards (e.g. LinkedIn, Indeed), agencies, referrals, internal applicants, prospecting…
List tracking links
Tool name:
list_tracking_linksTracking links are unique short URLs (e.g. https://grnh.se/ ) that an organization shares to attribute candidates to a source — campaign URLs, referral links, employee outreach, social posts, and…
List user emails
Tool name:
list_user_emailsUser emails are the email addresses attached to a Greenhouse user.
List user job permissions
Tool name:
list_user_job_permissionsUser job permissions are the per-user, per-job access grants that pair a user with a Job Admin role on a specific job.
List user roles
Tool name:
list_user_rolesUser roles are the organization-wide dictionary of access levels a user can hold — the categories themselves, not the per-user assignments.
List users
Tool name:
list_usersUsers are the Greenhouse accounts inside your organization — recruiters, hiring managers, interviewers, coordinators, sourcers, and site admins.
Move application
Tool name:
move_applicationAdvance the candidate to a new interview stage.
Reject application
Tool name:
reject_applicationReject an application and record the reason.
Replace approver approver group
Tool name:
replace_approver_approver_groupSwap one approver in an approver group for another user without rebuilding the rest of the approval flow — the V3 replacement for V1 PUT /v1/approval_flows/{id}/approver_groups/{id}/replace_approver.
Replace approver groups approval flow
Tool name:
replace_approver_groups_approval_flowWholesale-replace the ordered tiers of approvers on an existing approval flow — the V3 equivalent of rebuilding the flow's structure from an external HRIS.
Request approvals approval flow
Tool name:
request_approvals_approval_flowStart an existing pending approval flow by emailing its initial approver(s) and recording who requested the approvals.
Revoke user permissions
Tool name:
revoke_user_permissionsDemote a Site Admin to a Basic user, removing their organization-wide access.
Search applications
Tool name:
search_applicationsSearch applications in Greenhouse by candidate name, email, or other query text.
Search candidates
Tool name:
search_candidatesSearch candidates in Greenhouse by name, email, or other query text.
Search jobs
Tool name:
search_jobsSearch jobs in Greenhouse by name or other query text.
Unreject application
Tool name:
unreject_applicationReverse a rejection, putting the application back into the in-process state on the stage it was rejected from.
Update application
Tool name:
update_applicationPatch attribution and metadata fields on an existing application (source, referrer, recruiter, coordinator, prospect pool/stage, rejection date, custom fields).
Update approval flow
Tool name:
update_approval_flowToggle whether an existing approval flow is sequential (approver groups resolve one at a time in sort_order) or parallel (all groups activate at once).
Update blocked spam source
Tool name:
update_blocked_spam_sourceUpdates the note on a blocked spam source.
Update candidate
Tool name:
update_candidatePatch an existing candidate's profile fields.
Update custom field
Tool name:
update_custom_fieldEdit the definition of an existing custom field.
Update custom field option
Tool name:
update_custom_field_optionEdit the display label, sort order, or external id of an existing custom field option.
Update department
Tool name:
update_departmentUpdate an existing department's name, external_id, or position in the department tree.
Update interview
Tool name:
update_interviewPatch a scheduled interview's time, location, video conferencing link, external calendar event id, or interviewer panel.
Update job
Tool name:
update_jobPatch an existing job's editable fields.
Update job note
Tool name:
update_job_noteUpdate an existing job note.
Update job post
Tool name:
update_job_postEdit a job post in place — change its public title, replace its HTML body, or transition its publication status between draft and live.
Update offer
Tool name:
update_offerPatch fields on an existing offer.
Update office
Tool name:
update_officeUpdate an existing office.
Update opening
Tool name:
update_openingPatch an existing opening's editable fields, or change its status.
Update rejection detail
Tool name:
update_rejection_detailPatch the rejection reason or rejection question custom field answers on a rejected application without changing its rejected_at timestamp.
Update scorecard
Tool name:
update_scorecardPatch an existing scorecard.
Update scorecard candidate attribute
Tool name:
update_scorecard_candidate_attributeDeprecated — where available, prefer the nested candidate_attributes array on PATCH /v3/scorecards/{id}, which updates ratings by job_candidate_attribute_id with no row ids needed.
Update scorecard question answer
Tool name:
update_scorecard_question_answerDeprecated — where available, prefer the nested question_answers array on PATCH /v3/scorecards/{id}, which updates answers by scorecard_question_id with no answer-row ids needed.
Update user
Tool name:
update_userPatch an existing user's profile fields.
Compatibility
Connect Greenhouse to the clients your teams already use
27 AI clients can connect to Greenhouse through Runlayer. Pick one for its setup steps and controls.
Why Runlayer
Why connect Greenhouse through Runlayer?
One approved path
Approve Greenhouse once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.
Fine-grained policy
Control who can use each server, tool, and resource, and under which runtime conditions.
Runtime security
Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.
Audit and observability
Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.