zoho-recruit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOHO_REGION | No | Region for Zoho accounts and API (com, eu, in, au, jp, ca) | com |
| ZOHO_BASE_URL | No | Override API base URL (optional) | |
| ZOHO_CLIENT_ID | Yes | Client ID from Zoho API console | |
| ZOHO_ACCOUNTS_URL | No | Override accounts URL (optional) | |
| ZOHO_CLIENT_SECRET | Yes | Client Secret from Zoho API console | |
| ZOHO_REFRESH_TOKEN | Yes | Refresh token from OAuth flow |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_candidatesC | Search candidates in Zoho Recruit. Filter by free-text keyword, comma-separated skills, location, minimum years of experience, candidate status, or an associated job id. Example: "Find Python developers with 5+ years experience". |
| get_candidate_detailsB | Get a candidate's full profile: contact info, experience, skills, current company, status, and interview history. |
| create_candidateC | Create a new candidate profile in Zoho Recruit. |
| update_candidate_statusB | Move a candidate to a new stage (e.g. Applied, Screening, Assessment, Interview, Offer, Joined, Rejected). |
| bulk_candidate_updateA | Update many candidates at once. Each item must include an 'id' plus the fields to change, e.g. [{"id":"123","Candidate_Status":"Rejected"}]. Useful for "reject all candidates who failed assessment". |
| create_job_openingC | Create a new job opening in Zoho Recruit. |
| search_jobsA | Search job openings. Returns open positions, status, and the assigned recruiter. Use get_job_pipeline for the candidate pipeline of a job. |
| get_job_pipelineC | List the candidates currently associated with a job opening. |
| update_job_statusB | Update a job opening's status (e.g. Open, Hold, Closed). |
| move_candidate_in_pipelineB | Move a candidate to a new stage within a specific job's pipeline, e.g. "Move candidate to Technical Interview stage". |
| schedule_interviewC | Schedule an interview. |
| get_interview_scheduleB | List upcoming interviews and pending evaluations. Set
|
| submit_interview_feedbackA | Submit interview feedback. |
| hiring_funnel_reportC | Generate a hiring funnel: applicants, screening, interview, offers, joiners, rejections, and conversion percentages. Dates are YYYY-MM-DD. |
| recruiter_performance_reportB | Per-recruiter metrics: candidates sourced, interviews, offers, closures. |
| source_analysisC | Analyse candidate sources (LinkedIn, Naukri, Referral, Careers page) with per-source counts and join rates. |
| send_candidate_emailB | Send an email to a candidate. |
| resume_parserB | Parse a resume into structured JSON (skills, experience, companies, education, projects). Provide a base64-encoded PDF or raw text. |
| candidate_match_scoreB | Score a candidate against a job description. Returns match_percentage, strengths, gaps, and a recommendation. |
| interview_summary_generatorC | Turn an interview transcript into structured feedback: summary, strengths, concerns, and questions asked. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Most tools have distinct purposes, but update_candidate_status and move_candidate_in_pipeline overlap in moving candidates through stages, though the latter is job-specific. Some tools like get_job_pipeline and hiring_funnel_report relate to pipelines but are clarified by descriptions.
Tools predominantly follow verb_noun pattern (create, get, search, update, schedule, send, submit, move). A few use noun_noun (interview_summary_generator, source_analysis) but remain descriptive. Overall consistent and predictable.
20 tools cover candidate management, job openings, interviews, email, and reporting without feeling excessive. Each tool serves a clear purpose within the recruiting domain.
Core recruiting lifecycle is well-covered: create/update/search candidates and jobs, schedule/submit feedback, reports. Missing delete operations (candidates, jobs) and explicit offer management, but these are minor gaps.