Job Search MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| USER_AGENT | No | User agent string for web scraping | |
| REQUEST_TIMEOUT | No | Request timeout in milliseconds | 30000 |
| RATE_LIMIT_PER_MINUTE | No | Rate limiting for requests | 30 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_ai_ml_jobsC | Search for AI/ML internships and full-time roles across multiple job sites |
| search_specific_job_siteC | Search for jobs on a specific job site |
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 2 tools
The two tools have overlapping purposes, as both are for searching jobs, with one being a general AI/ML search and the other for specific sites. This creates ambiguity—an agent might struggle to choose between them when searching on a particular site, as the descriptions don't clearly delineate when to use each tool.
Both tools follow a consistent snake_case naming pattern with 'search' as the verb, which is predictable and readable. However, the slight inconsistency in naming (e.g., 'search_ai_ml_jobs' vs. 'search_specific_job_site') is minor, as they maintain a clear verb_noun structure.
With only 2 tools, the server feels thin for a job search domain, lacking essential operations like filtering, applying, or managing job listings. This limited scope suggests the tool set is underdeveloped and may not support comprehensive agent workflows.
The tool set is severely incomplete for job searching, missing critical functions such as filtering by location or salary, applying to jobs, saving listings, or tracking applications. This will likely cause agent failures in handling typical job search tasks beyond basic searches.