JobDataLake MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JDL_API_KEY | Yes | Your JobDataLake API key (get a free key at jobdatalake.com) |
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 |
|---|---|
| search_jobsB | Search 1M+ job listings from 20K+ companies. Supports keyword search, AI semantic search, filters for location, salary, remote type, seniority, skills, and more. |
| get_jobC | Get full details for a specific job listing including description, requirements, salary, and apply link. |
| get_companyB | Get company profile including open job count, industry, size, and career page URL. |
| find_similar_jobsA | Find jobs similar to a given job listing using AI vector similarity. Great for "more like this" discovery. |
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 has a clearly distinct purpose: find_similar_jobs focuses on AI-based similarity matching for job discovery, get_company retrieves company profiles, get_job fetches specific job details, and search_jobs handles broad keyword/semantic search with filtering. There is no overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., find_similar_jobs, get_company, get_job, search_jobs). The verbs (find, get, search) are appropriately descriptive and maintain a predictable naming convention throughout the set.
With 4 tools, the server is well-scoped for job data exploration, covering key operations like searching, retrieving details, finding similar items, and company profiling. It feels slightly lean but reasonable, as core workflows are supported without unnecessary bloat.
The toolset provides comprehensive coverage for job data querying and discovery, including search, detailed retrieval, similarity matching, and company context. Minor gaps exist, such as no explicit update or delete operations, but these are likely unnecessary for a read-only data lake, and agents can work effectively with the available tools.