Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ZOHO_REGIONNoRegion for Zoho accounts and API (com, eu, in, au, jp, ca)com
ZOHO_BASE_URLNoOverride API base URL (optional)
ZOHO_CLIENT_IDYesClient ID from Zoho API console
ZOHO_ACCOUNTS_URLNoOverride accounts URL (optional)
ZOHO_CLIENT_SECRETYesClient Secret from Zoho API console
ZOHO_REFRESH_TOKENYesRefresh 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. date is YYYY-MM-DD and time is HH:MM (24h, with optional timezone offset, e.g. 14:30:00+05:30).

get_interview_scheduleB

List upcoming interviews and pending evaluations. Set pending_feedback_only=true to show interviews awaiting feedback.

submit_interview_feedbackA

Submit interview feedback. recommendation is typically one of Hire / No Hire / Hold. Pass interview_id to update an existing interview record instead of creating one.

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. template is one of rejection, interview_invitation, follow_up, offer (used to derive a subject), or pass a Zoho template_id for a branded template. Provide message for an ad-hoc body.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 20 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count5/5

20 tools cover candidate management, job openings, interviews, email, and reporting without feeling excessive. Each tool serves a clear purpose within the recruiting domain.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessNo issues