hiringindex-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | No | Alternative API key for the Hiring Index marketplace (also accepted as HIRINGINDEX_API_KEY). | |
| HIRINGINDEX_HOST | No | Marketplace host. | hiringindex.p.rapidapi.com |
| HIRINGINDEX_API_KEY | No | API key for the Hiring Index marketplace (also accepts RAPIDAPI_KEY). | |
| HIRINGINDEX_API_BASE | No | Set this to call our backend directly instead of the marketplace; switches auth from x-rapidapi-key to x-api-key. | |
| HIRINGINDEX_TIMEOUT_MS | No | Request timeout in milliseconds. | 30000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Search live job postings read directly from ten applicant tracking systems (Workday, SmartRecruiters, Greenhouse, Workable, Lever, Ashby, Recruitee, Teamtailor, Breezy, Personio). Returns title, employer where the ATS publishes it, location, employment type, advertised salary where disclosed, posting date and the employer's own apply link where the source carries one. |
| job_market_insightsA | Counts, salary percentiles by currency, remote share, top employers, seniority and employment-type mix, city and source split for any slice of postings. Accepts the same filters as search_jobs. Use this instead of paging through results when the question is about the market rather than about individual roles. |
| posting_age_reportA | Age profile of a slice of postings: median days since publication, share posted in the last week, and share still open after sixty days. A listing that has been open for months is the most commonly cited sign that a role is not being actively filled — this reports the numbers rather than guessing. |
| get_jobA | Full detail for a single posting by its id, including the description and the application link. |
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 4 tools
Each tool targets a distinct question: individual postings, aggregate market stats, single-post detail, and posting-age distribution. The overlap between search_jobs and job_market_insights is explicitly addressed in the descriptions, so an agent can reliably select the right tool.
Two tools use an imperative verb_noun pattern (search_jobs, get_job), while the other two use descriptive noun phrases (job_market_insights, posting_age_report). This is a minor convention split, but the names are still clear and the pattern is readable.
Four tools is well-scoped for a read-only job-market data server. Each tool covers a distinct and necessary operation without redundancy or bloat.
For the stated domain of job posting search and market analysis, the surface is complete: search, detail retrieval, aggregate insights, and posting-age reporting cover the core workflows. No obvious dead ends or missing lifecycle steps exist for this read-only domain.