Glassdoor MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HASDATA_API_KEY | Yes | HasData API key, created free at https://app.hasdata.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 |
|---|---|
| hasdata_glassdoor_job_getJobDetailsA | Get GlassDoor Job Details Fetches a Glassdoor job posting by its vacancy URL. Returns job title, company name and rating, location, salary estimate, employment type, posted date, full job description, qualifications/benefits, and apply link. Use for ATS ingestion, job aggregators, comp benchmarking, enrichment of company profiles, and feeding descriptions into LLM matching or resume-tailoring pipelines. |
| hasdata_glassdoor_listing_getJobListingsA | Get GlassDoor Job Listings Searches Glassdoor job listings by keyword and location with sort (recent/relevant), domain targeting, and nextPageToken pagination. Returns an array of jobs with title, company, location, salary estimate, posted date, job URL, and jobId, plus the next page token. Use to build job feeds, monitor hiring trends for roles/companies/regions, power candidate sourcing tools, and collect URLs for downstream full-detail scraping via the Glassdoor Job endpoint. |
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 completely distinct purposes: one searches and returns job listings, the other fetches full details for a specific job by URL. There is no overlap or ambiguity between them.
Both tool names follow the same pattern: hasdata_glassdoor_<resource>_<verb>. The resource (job/listing) and action (getJobDetails/getJobListings) are clearly and consistently structured, despite using camelCase for the verb portion.
Two tools is on the low end, but for a narrowly scoped Glassdoor job data server, this pair covers the essential search-and-detail workflow. It feels appropriately minimal rather than incomplete.
The server covers the core job data lifecycle from discovery (listings with pagination) to retrieval (full details). For a read-only job data source, there are no obvious missing operations—the two endpoints form a complete workflow.