Greenhouse MCP is in open beta. The prompts in this article reflect open beta capabilities and may change.
Note: What a prompt can do depends on your organization's enabled scopes and your Greenhouse permissions.
Use these prompts to start working with Greenhouse MCP. They are written for Talent Ops, recruiters, coordinators, and hiring managers. They work in any AI tool connected to Greenhouse MCP, including Claude, ChatGPT, Copilot Studio, Glean, Google Antigravity, Amazon Q, and Grok.
Replace the [bracketed] placeholders with your own jobs, candidates, and dates.
Read only prompts pull and analyze data. They are safe to try first. Writes data prompts change records in Greenhouse and always ask the AI to preview the change and wait for your approval.
For more examples grouped by role, see Greenhouse MCP use cases by role.
Examples from the Greenhouse Talent Ops team
These prompts come from the Greenhouse Talent Ops team. Each one includes tips for getting better results.
Live KPI dashboard
Read only: Build a live dashboard of your recruiting KPIs.
Build me a live artifact called "Q4 2026 TP&A KPI Dashboard" that pulls data from Greenhouse Recruiting through the MCP. Scope everything to Q4 2026 (Oct 1 - Dec 31).
Tips:
- Define your KPIs and jargon.
- Say which fields to use.
- Give goals and thresholds up front.
- Build in stages and check the outputs along the way.
Approval updates
Writes data: Bulk-update approvers across roles in Greenhouse while maintaining full governance.
Update the approval chain in Greenhouse for all roles that have a status of Open or Draft. Swap Michelle for Amanda and Shannon for Marie.
Uses: Jobs, approvals
Tips:
- Try it on just one search first.
- When performing actions on one job, use job IDs instead of job names.
Hiring funnel report
Read only: See where candidates are in the hiring funnel for a job.
Build me a hiring funnel dashboard for a Greenhouse job. I'll type in a job ID and it should show how many candidates are in each interview stage, how many candidates have been rejected and why, interviews still waiting on feedback, and a timeline from the job's open date to the offer delivery date.
Uses: Jobs, candidates, scorecards
Tips:
- When accessing one job, use job IDs instead of job names.
- Connect to other resources to make the dashboard information and context-rich.
- Add refinements after the first version.
Talent Ops
For recruiting operations, TA leaders, and people analytics. Audit data quality, find process bottlenecks, and prototype reporting before you build a permanent report.
Data quality and job setup
Job setup audit
Read only: Find active jobs with gaps that hurt reporting and compliance.
In Greenhouse, list every open job and flag any that are missing an external job post, a hiring manager, a recruiter, an office, a department, or any required custom job fields. Return a table with job ID, job name, department, and the missing items. Sort by the number of gaps, most first. Omit template jobs from results.
Uses: Jobs, job posts, hiring teams
Interview stage naming check
Read only: Inconsistent stage names make pipeline analysis unreliable.
Pull the interview stages for all open jobs in Greenhouse. Group stages that look like the same step under different names (for example, "Phone Screen" vs. "Recruiter Screen"). Show each group, the jobs that use each variant, and suggest one standard name per group.
Uses: Jobs, job stages
Rejection reason hygiene
Read only: Missing or vague reasons hide where and why candidates drop off.
For applications rejected in Greenhouse in the last [90] days, show what share have a rejection reason, broken down by department and by stage. List the 10 most-used rejection reasons and flag any jobs where more than [20]% of rejections have no reason.
Uses: Applications, rejection reasons
Custom field completeness
Read only: Audit usage of custom candidate fields.
For candidates that have reached [stage name] stage, return a table of custom candidate field names, object (candidate or application field), % complete, and the recruiters with the lowest completion rate.
Uses: Candidates, custom fields
Possible duplicate candidates
Read only: Spot likely duplicates for review without merging anything.
Search Greenhouse for candidates who applied in the last [60] days and may be duplicates: same email, or same full name with a matching phone number or LinkedIn URL. List each likely pair with candidate IDs and the matching fields. Do not merge anything.
Uses: Candidates
Process bottlenecks
Offer approval bottlenecks
Read only: Find which approvers slow offers down.
For offers created in Greenhouse in the last [90] days, identify who are the biggest bottlenecks in our offer approval chain, and which departments are most affected? List the jobs most impacted including job name, recruiter, hiring manager, and approvers, include time between approval steps.
Uses: Offers, approvals
Recruiter bottlenecks
Read only: See where stalled candidates are piling up.
In Greenhouse, which recruiters have the most active candidates who haven't moved stages in the last [7] days? Group by recruiter and stage, and include each recruiter's total active candidates so I can compare load.
Uses: Applications, jobs, users
Scorecard accountability
Read only: Check feedback completion and consistency by interviewer.
For interviews in Greenhouse in the last [30] days, show which hiring managers and interviewers submitted scorecards, which didn't, median hours from interview to submission, and the mix of recommendations (strong yes to strong no) per person. Highlight interviewers with the lowest completion rates and those with a high percentage of strong nos or strong yeses.
Uses: Scorecards, scheduled interviews
Time to fill by department
Read only: A fast read on hiring speed without building a report.
For jobs closed in Greenhouse in the last [6 months], calculate days from job open date to first hire, grouped by department. Show median, fastest, and slowest, and list any job that took more than [90] days. Make sure to double check your math.
Uses: Jobs, applications, offers
Source effectiveness
Read only: Learn which sources produce hires, not just applicants.
For applications created in Greenhouse in the last [6 months], group by source. Show applications, candidates who reached an onsite or final stage, and hires for each source, plus the pass through rate at each stage. Highlight the top 3 sources of hires. Make sure to double check your math.
Uses: Applications, sources
Reporting and updates
Live pipeline dashboard
Read only: A team-wide view of open reqs, ready for a leadership sync.
Build a dashboard of all open jobs in Greenhouse for [department or team]. For each job show days open, candidates by stage, the most advanced candidate, and a flag for jobs with no new applicants in [14] days.
Uses: Jobs, applications
Weekly ops digest
Read only: A repeatable summary you can post every Monday.
Write a weekly recruiting ops summary from Greenhouse for the last 7 days: jobs opened and closed, new applications, candidates hired, offers created, and stalled candidates. End with the 3 items that most need attention this week. Keep it under 200 words.
Uses: Jobs, applications, offers
User access review
Read only: A quick audit of user access and user details captured in Greenhouse.
Make a table of Greenhouse active users with links to their user profiles. Group users by permission level. In the table include permission level, future job permissions, and all custom user fields and interview groups. Additionally, identify any disabled users who still appear on a hiring team for an open job or in any approval chains.
Uses: Users, jobs
User job title audit
Read only: Identify interviewers who do not have their job title saved in Greenhouse.
Make a list of active Greenhouse site admins, job admins, or basic users who have been scheduled to interview candidates in the last [180] days who have an empty job title field in their Account Settings.
Uses: Users
Recruiters
Review pipeline movement, prepare for screens and debriefs faster, and keep hiring managers informed without opening every req.
Daily pipeline
Morning pipeline brief
Read only: Start the day knowing exactly where to focus.
Catch me up on my open jobs in Greenhouse where I'm the recruiter. For each job, show candidates by stage, new applicants since [yesterday], and anyone waiting on me (for example a completed interview with no next step). End with my top 5 actions for today.
Uses: Jobs, applications, hiring teams
Stalled candidate check
Read only: Catch candidates before they go cold.
Show how long candidates have been in their current stage for all my active jobs in Greenhouse. Flag anyone in the same stage for more than [10] days and group them by job and stage, longest wait first.
Uses: Applications, jobs
Offer tracker
Read only: Keep every pending offer moving.
List all open offers in Greenhouse for my jobs: candidate, job, offer status, date created, approval status, and days since the last update. Flag offers waiting on approval for more than [3] days.
Uses: Offers, applications
Source report for my reqs
Read only: See which sources work for the roles you own.
For my open jobs in Greenhouse, break down active candidates by source and by stage. Which sources are producing candidates who pass the [recruiter screen]? Show it as a table per job.
Uses: Applications, sources
Candidate review
Debrief prep pack
Read only: Walk into a debrief with the disagreements already surfaced.
Prepare me for the debrief for [candidate name] on job [req ID]. Summarize every submitted scorecard, show where interviewers agree and disagree by attribute, list interviewers who haven't submitted yet, and suggest 3 questions to resolve in the meeting.
Uses: Scorecards, scheduled interviews
Compensation mismatch warning
Read only: Spot comp risk before it slows the process.
For candidates in my active pipeline in Greenhouse who listed a desired salary, flag anyone whose expectation is above the midpoint of the posted range for that job. Show candidate, job, stage, desired salary, and posted range.
Uses: Applications, custom fields, job posts
Silver medalist rediscovery
Read only: Re-engage strong past finalists for a new opening.
Find candidates in Greenhouse who reached the [final interview or offer] stage for jobs similar to [job ID or title] in the last [12 months] but weren't hired. Show their name, previous job, furthest stage, rejection reason, and date. Exclude anyone rejected for [reason, e.g. "Not a culture add"].
Uses: Candidates, applications, rejection reasons
Communication and actions
Hiring manager weekly update
Read only: A ready-to-send update for each hiring manager.
Draft a weekly update for the hiring manager on job [req ID] using Greenhouse data: pipeline by stage, movement since last week, top candidates, scheduled interviews this week, and anything I need from them. Keep it short and friendly. Don't send it, just draft it.
Uses: Jobs, applications, scheduled interviews
Log a call note
Writes data: Keep the candidate record current right after a call.
Add a note to [candidate name]'s Greenhouse profile from my call today: [paste call notes]. Clean it into 3 to 5 bullets covering motivation, timing, compensation, and concerns. Show me the note first and add it only after I confirm.
Uses: Candidates, notes (write)
Missing scorecards
Read only: Close feedback gaps so debriefs aren't delayed.
List interviews completed in Greenhouse more than [24 hours] ago that still have no scorecard from one or more interviewers. Show interviewer, candidate, job, interview date, and hours overdue. Then draft a friendly reminder for each interviewer that groups all their overdue scorecards in one message.
Uses: Scorecards, scheduled interviews
Job setup review
Interview kit consistency audit
Read only: Find missing or inconsistent kits across similar roles.
Compare the interview kits across all my jobs in Greenhouse. Identify stages with limited or no interview kits at all. Look for focus attributes, custom questions, and default interviewers.
Hiring team roster
Read only: Confirm the right people are on each job.
For my open jobs in Greenhouse, list the hiring manager, recruiter, coordinator, and sourcer. Flag jobs missing any of those roles and any hiring team member whose Greenhouse user is disabled.
Uses: Jobs, hiring teams, users
Role reality check
Read only: Make sure the job reflects how the team works today. Requires Slack or Google Drive connectors to be configured.
Compare the job description and interview kit for job [job ID] in Greenhouse against our current team priorities: [paste priorities, or ask the AI to use connected Slack or Drive docs]. What looks outdated, missing, or overemphasized?
Uses: Jobs, job posts, interview kits
Interview questions by attribute
Read only: Sharper questions tied to what you're scoring.
Pull the scorecard attributes for the [stage name] stage of job [job ID] in Greenhouse. For each attribute, suggest 2 behavioral questions and what a strong vs. weak answer looks like.
Uses: Jobs, interview kits
Rejection pattern review
Read only: Learn why candidates aren't making it through.
For job [job ID], show rejection reasons in Greenhouse by stage over the last [90] days. Where are most candidates falling out, and what does that suggest about the job requirements or the interview plan?
Uses: Applications, rejection reasons
Coordinators
Keep interviews on track, close feedback gaps, and catch setup problems before they reach candidates.
Schedule and RSVPs
This week's interview schedule
Read only: One list of everything you're coordinating.
List all interviews scheduled in Greenhouse for [this week] on jobs I coordinate: date and time, candidate, job, stage, and interviewers. Group by day and flag any interview where the interviewer has not accepted or has declined the interview.
Uses: Scheduled interviews, jobs
Interviewer load check
Read only: Spread interviews fairly and avoid burnout.
Count interviews per interviewer in Greenhouse over the last [30] days and the next [14] days. Show the top 15 interviewers by volume and flag anyone with more than [8] interviews in a week.
Uses: Scheduled interviews, users
Candidate experience
Onsite prep email
Read only: A clear, accurate itinerary for the candidate.
Draft a prep email for [candidate name] for their [onsite / final round] on job [job ID]. Use the interviews scheduled in Greenhouse to list each session's time, interviewer name and title, and focus area. Keep the tone warm and include a line on who to contact with questions. Draft only.
Uses: Scheduled interviews, jobs
Hiring managers
Get a quick read on your open jobs, review candidates with full context, and make faster, better-supported decisions.
Stay current
Catch me up on my reqs
Read only: One view of every job you own.
Catch me up on all my open jobs in Greenhouse. For each one, show pipeline by stage, which candidates are closest to offer, expected start date if known, and any risks or actions needed from me this week.
Uses: Jobs, applications, offers
My open scorecards
Read only: Never be the reason a debrief slips.
List any interviews I've conducted in Greenhouse where my scorecard isn't submitted yet. Show the candidate, job, interview date, and how many days ago it happened. Oldest first.
Uses: Scorecards, scheduled interviews
Is this req on track?
Read only: Benchmark a job against your past hiring.
For job [job ID], compare the current pipeline in Greenhouse to similar jobs I've hired for in the last [12 months]: days open, applicants per stage, and stage-to-stage conversion. Tell me whether this job is ahead of or behind, and where the pipeline is thin.
Uses: Jobs, applications
Evaluate candidates
Candidate and debrief summary
Read only: All the feedback in one plain-language summary.
Summarize [candidate name] for job [job ID]. Pull scorecards, interview notes, and debrief feedback from Greenhouse. Show where interviewers agree or disagree, what risks are still open, and what decision points I should focus on.
Uses: Scorecards, candidates, notes
Compare finalists
Read only: See your top candidates side by side.
Compare the finalists for job [job ID] in Greenhouse: [candidate A], [candidate B], [candidate C]. Build a table with each scorecard attribute as a row, each candidate's ratings and the overall recommendations. Then summarize the strongest case for each and the biggest open question.
Uses: Scorecards, applications
Hiring decision memo
Read only: Document the reasoning behind your choice.
Draft a short hiring decision memo for [candidate name] on job [job ID] using their Greenhouse scorecards and notes: recommendation, evidence for each key attribute, risks and how we'll mitigate them, and any dissenting feedback. Under 300 words.
Uses: Scorecards, notes
Add-on lines for any prompt
Paste one of these lines at the end of any prompt to control format, safety, or scope.
| Add-on | Line to paste |
| Preview before saving | Before changing anything in Greenhouse, show me exactly what you will change and wait for me to say yes. |
| Table output | Return the results as a table I can paste into a spreadsheet, with one row per [job / candidate]. |
| Show your sources | List which Greenhouse data you used, and tell me if anything was missing or you didn't have access. |
| Limit to my work | Only include jobs where I'm on the hiring team. |
| Exclude test data | Exclude test jobs, template jobs, and prospects. |
| Shareable summary | Rewrite this as a 5-bullet summary I can share in Slack or email. |
| Check the math | Show the counts behind every percentage so I can verify them in Greenhouse. |
| Link to profile or job dashboard | Include links to candidate profiles and jobs in the response. |
Before you start
Get connected
- A Site Admin connects Greenhouse MCP and enables scopes in Dev Center > MCP Access.
- Sign in with the email tied to your Greenhouse Recruiting account.
- If your admin changes scopes, disconnect and reconnect to pick them up.
- Greenhouse MCP is available on Core, Plus, and Pro subscription tiers and is in open beta.
Write prompts that land
- Say "in Greenhouse" so the AI uses the Greenhouse tools, not the web.
- Use job IDs or exact job names. They are less ambiguous than nicknames.
- Give a time window ("last 30 days") and an output shape (table, bullets, draft).
- Ask follow-ups in the same chat. The AI keeps the data it already pulled.
Use write actions with care
- Start with read prompts. Move to write prompts once results look right.
- Ask for a preview of every change and approve it before anything is saved.
- Rejecting, hiring, merging, and anonymizing candidates always require your confirmation.
- Deleting records isn't available through MCP.
Know the current limits
- Resume and attachment contents aren't readable through MCP today.
- Bulk actions aren't supported for most actions. Some updates, such as approval chains, can cover many jobs in one request. Actions such as rejecting candidates, moving applications, tagging candidates, updating candidate profiles, and adding notes run one record at a time.
- API-only custom fields can't be edited through MCP.
- Output quality follows data quality. Consistent stage names, complete scorecards, and rejection reasons matter.