create_screening_role
Set up a screening role to rank CVs against a job description. Specify must-have skills, experience, and requirements to score candidates objectively.
Instructions
Create a Screening — a role to rank CVs against a JD before spending any interview credit. Returns {"roleId": , ...}; keep that roleId for the rest of the flow.
THE SCREENING FLOW (call these tools in order):
1. create_screening_role ← you are here
2. parse_cvs(files=...) — extract candidates from resume files
3. add_screening_candidates(role_id, candidates=<parse_cvs rows>)
4. run_screening(role_id) — starts async CV-vs-JD scoring
5. get_screening_results(role_id) — poll until scored, read the ranking
6. schedule_screened_candidates(role_id, candidate_ids) — invite the good ones
FIELDS:
- name: the screening / role title (required, e.g. "Senior Backend Engineer").
- job_description: paste the full JD text if you have it — it drives the
score most. Optional but strongly recommended.
- must_have_skills vs nice_to_have_skills: skills the role weighs heavily
vs would-be-nice. Neither AUTO-REJECTS anyone — they shape the LLM
score and the matched/related/missing breakdown.
- experience: free text, e.g. "5+ years".
- location + work_mode: work_mode is 'remote', 'onsite', or 'hybrid'.
Location is a soft signal only (a remote role ignores it); nobody is
dropped for being in the wrong city.
- additional_requirements: free text the model folds into scoring, e.g.
"valid work visa", "bachelor's degree", "AWS certified".
- language: 'en', 'hi', or 'ar'. company_name: optional.
This creates a role record (screening_enabled). If the user already has a
screening for this opening, call list_screening_roles first and reuse its
roleId instead of making a duplicate.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| language | No | en | |
| location | No | ||
| work_mode | No | ||
| experience | No | ||
| company_name | No | ||
| job_description | No | ||
| must_have_skills | No | ||
| nice_to_have_skills | No | ||
| additional_requirements | No |