bach-jsearch
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| job_detailsA | Get all job details, including additional information such as: application options / links, employer reviews and estimated salaries for similar jobs. |
| job_searchA | Search for jobs posted on any public job site across the web on the largest job aggregate in the world (Google for Jobs). Extensive filtering support and most options available on Google for Jobs. |
| job_salaryA | Get estimated salaries / pay for a jobs around a location by job title and location. The salary estimation is returned for several periods, depending on data availability / relevance, and includes: hourly, daily, weekly, monthly, or yearly. |
| company_job_salaryA | Get estimated job salaries/pay in a specific company by job title and optionally a location and experience level in years. |
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
The tools are mostly distinct: job_search finds jobs, job_details retrieves details for a specific job, job_salary estimates salary by title/location, and company_job_salary estimates salary by company/title. However, job_salary and company_job_salary both deal with salary estimation, and job_details also includes salary estimates, creating minor overlap.
All tools use lowercase snake_case with a descriptive prefix. job_search uses a verb (search), while job_details and job_salary use nouns, and company_job_salary combines company and job. The pattern is readable but not perfectly uniform.
With only 4 tools, the server is well-scoped for a job search API. Each tool serves a distinct, essential function (search, details, salary by title, salary by company) without unnecessary proliferation.
The tool set covers the core job-search lifecycle: searching, viewing details, and salary estimation. Minor gaps exist, such as lack of tools for managing saved searches or applying to jobs, but for a search-focused server the coverage is solid.