Jobs Every Hour MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| latest_jobsB | The newest open jobs on Jobs Every Hour, read every hour from employers' own career pages (Greenhouse, Lever, Ashby, Workday, iCIMS and more). |
| jobs_by_skillA | Open jobs that ask for a skill, such as Python, React, SQL, Kubernetes or Salesforce. |
| jobs_by_categoryA | Open jobs in a field of work, such as engineering, design, sales, marketing, healthcare or operations. |
| jobs_by_locationA | Open jobs in a country, region or large city, such as united-states, europe, london, new-york or remote. |
| jobs_by_companyA | Open jobs at one employer, read from its own career page. |
| list_feedsB | The skills, categories, locations or companies that have a feed, with the number of open jobs in each. |
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 6 tools
Each tool targets a distinct facet of the job corpus (recency, skill, category, location, company) plus a metadata tool, so an agent can map intent to tool without guessing. The only near-overlap is latest_jobs versus a filtered query, but its description makes the recency purpose unambiguous.
Five of six tools follow a clear jobs_by_<dimension> pattern with a final list_feeds verb_noun tool. latest_jobs deviates slightly but remains readable and conventional in snake_case, so the set is predictable overall.
Six tools is well within the ideal range and each maps to a genuine search dimension; none feels redundant or bolted on. list_feeds also earns its place by exposing valid filter values.
The surface covers listing and faceted filtering but has no way to retrieve a single job's full detail by id, nor keyword/title or salary/date-range search, which are common job-search needs. Agents can still do broad discovery, but deeper lookups or refinement are dead ends.