HasData

glassdoor_listing: GET /

hasdata_glassdoor_listing_getJobListings

Get GlassDoor Job Listings

Searches Glassdoor job listings by keyword and location with sort (recent/relevant), domain targeting, filters (date posted, distance, salary range, company rating, easy apply, remote), and nextPageToken pagination that keeps the filters. 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.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	The sorting option for the search results.
`domain`	No	The domain of the Glassdoor site (optional).
`radius`	No	Search radius around the location, in miles. `0` keeps only jobs in the location itself. Glassdoor uses 25 miles when this is not set.
`keyword`	Yes	The keyword used to search for job listings.
`location`	Yes	The location to search for job listings.
`maxSalary`	No	Upper bound of the yearly pay range, must be greater than `minSalary`. Can be used on its own.
`minRating`	No	Returns jobs from companies rated at least this high. Glassdoor applies the filter approximately, so a few companies rated slightly below the value can appear.
`minSalary`	No	Lower bound of the yearly pay range. A job is kept when its estimated pay range overlaps the requested one; hourly and monthly pay are converted to yearly. Jobs without a pay estimate are excluded when a salary filter is set.
`datePosted`	No	Returns only jobs posted within the given number of days.
`remoteOnly`	No	Returns only remote jobs. Defaults to false.
`easyApplyOnly`	No	Returns only jobs that can be applied to directly on Glassdoor. Defaults to false.
`nextPageToken`	No	Token for fetching the next page of jobs, taken from the pagination of a previous response. The token keeps the filters of the search it came from, so they do not need to be sent again.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 1, 2026

addedInput schema / properties / datePosted

Added value: +{
+  "description": "Returns only jobs posted within the given number of days.",
+  "enum": [
+    1,
+    3,
+    7,
+    14,
+    30
+  ],
+  "type": "number"
+}

addedInput schema / properties / easyApplyOnly

Added value: +{
+  "description": "Returns only jobs that can be applied to directly on Glassdoor. Defaults to false.",
+  "type": "boolean"
+}

addedInput schema / properties / maxSalary

Added value: +{
+  "description": "Upper bound of the yearly pay range, must be greater than `minSalary`. Can be used on its own.",
+  "type": "number"
+}

addedInput schema / properties / minRating

Added value: +{
+  "description": "Returns jobs from companies rated at least this high. Glassdoor applies the filter approximately, so a few companies rated slightly below the value can appear.",
+  "enum": [
+    1,
+    2,
+    3,
+    4
+  ],
+  "type": "number"
+}

addedInput schema / properties / minSalary

Added value: +{
+  "description": "Lower bound of the yearly pay range. A job is kept when its estimated pay range overlaps the requested one; hourly and monthly pay are converted to yearly. Jobs without a pay estimate are excluded when a salary filter is set.",
+  "type": "number"
+}

changedInput schema / properties / nextPageToken / description

Previous value: -"Token for fetching the next page of jobs."New value: +"Token for fetching the next page of jobs, taken from the pagination of a previous response. The token keeps the filters of the search it came from, so they do not need to be sent again."

addedInput schema / properties / radius

Added value: +{
+  "description": "Search radius around the location, in miles. `0` keeps only jobs in the location itself. Glassdoor uses 25 miles when this is not set.",
+  "enum": [
+    0,
+    5,
+    10,
+    15,
+    25,
+    50,
+    100
+  ],
+  "type": "number"
+}

addedInput schema / properties / remoteOnly

Added value: +{
+  "description": "Returns only remote jobs. Defaults to false.",
+  "type": "boolean"
+}

First observedSep 8, 2026

TDQS

A3.9/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It usefully discloses the return fields and the non-obvious pagination behavior (the nextPageToken preserves prior filters), but says nothing about authentication requirements, rate limits, quota costs, or failure modes for a 12-parameter scraping endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight paragraphs, front-loaded with the core action before filters and use cases. The use-case list is slightly padded but each element (feeds, trend monitoring, sourcing, URL collection) maps to a distinct consumer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter search tool with no output schema, the description compensates by enumerating returned fields (title, company, location, salary estimate, posted date, URL, jobId, next page token) and explaining pagination filter retention. Missing only auth/error context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter is already documented in structured form, including enum meanings and the salary-overlap and approximate-rating caveats. The description adds only a high-level restatement of filter categories rather than syntax or semantics beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Searches Glassdoor job listings by keyword and location') and enumerates the search axes (sort, domain, filters, pagination). It also implicitly distinguishes itself from the sibling hasdata_glassdoor_job_getJobDetails by positioning this tool as the list-level endpoint feeding detail scraping.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases (build job feeds, monitor hiring trends, candidate sourcing) and explicitly routes downstream detail fetching to the Glassdoor Job endpoint sibling, which is exactly the alternative-selection guidance an agent needs. It stops short of stating when NOT to use it (e.g., when you already have a jobId).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HasData tools Inspect

Try in Browser

Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

glassdoor_listing: GET /

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources