HasData

indeed_listing: GET /

hasdata_indeed_listing_getJobListings

Read-only

Get Indeed Job Listings

Searches Indeed job listings by keyword and location with sort (relevance/date), country domain targeting, date-posted (1/3/7/14 days) and remote/hybrid filters, and offset-based pagination (start). Returns an array of jobs with title, company, location, salary, posted date, job URL, sponsored flag, and jobKey (Indeed's stable job id, the only reliable dedup key for sponsored postings) for the requested page. With sponsoredOnly the request exits from the domain's country, where Indeed serves Canadian searches as sponsored postings. Use for job-market dashboards, role/geo hiring-trend analysis, sourcing pipelines, and generating URL lists to feed into the Indeed Job endpoint.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	The sorting option for the search results.
`start`	No	The starting index of the results to retrieve (optional).
`domain`	No	The domain of the Indeed site (optional). Provide one exact documented value (62 allowed), e.g. `ar.indeed.com`, `au.indeed.com`.
`keyword`	Yes	The keyword used to search for job listings.
`location`	Yes	The location to search for job listings.
`datePosted`	No	Returns only jobs posted within the given number of days.
`remoteType`	No	Returns only remote (`remote`) or hybrid (`hybrid`) jobs. In the US, Indeed ties fully remote jobs to the country rather than a city, so use a country-wide location such as `United States`: with a city, Indeed returns few or no remote jobs.
`sponsoredOnly`	No	When enabled, the request is made in a way that returns more sponsored listings. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / datePosted

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

addedInput schema / properties / remoteType

Added value: +{
+  "description": "Returns only remote (`remote`) or hybrid (`hybrid`) jobs. In the US, Indeed ties fully remote jobs to the country rather than a city, so use a country-wide location such as `United States`: with a city, Indeed returns few or no remote jobs.",
+  "enum": [
+    "remote",
+    "hybrid"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sponsoredOnly

Added value: +{
+  "description": "When enabled, the request is made in a way that returns more sponsored listings. Defaults to false.",
+  "type": "boolean"
+}

Changed2 schema fields changedJul 24, 2026

changedInput schema / properties / domain / description

Previous value: -"The domain of the Indeed site (optional)."New value: +"The domain of the Indeed site (optional). Provide one exact documented value (62 allowed), e.g. `ar.indeed.com`, `au.indeed.com`."

removedInput schema / properties / domain / enum

Removed value: -[
-  "ar.indeed.com",
-  "au.indeed.com",
-  "at.indeed.com",
-  "bh.indeed.com",
-  "be.indeed.com",
-  "br.indeed.com",
-  "ca.indeed.com",
-  "cl.indeed.com",
-  "cn.indeed.com",
-  "co.indeed.com",
-  "cr.indeed.com",
-  "cz.indeed.com",
-  "dk.indeed.com",
-  "ec.indeed.com",
-  "eg.indeed.com",
-  "fi.indeed.com",
-  "fr.indeed.com",
-  "de.indeed.com",
-  "gr.indeed.com",
-  "hk.indeed.com",
-  "hu.indeed.com",
-  "in.indeed.com",
-  "id.indeed.com",
-  "ie.indeed.com",
-  "il.indeed.com",
-  "it.indeed.com",
-  "jp.indeed.com",
-  "kw.indeed.com",
-  "lu.indeed.com",
-  "malaysia.indeed.com",
-  "mx.indeed.com",
-  "ma.indeed.com",
-  "nl.indeed.com",
-  "nz.indeed.com",
-  "ng.indeed.com",
-  "no.indeed.com",
-  "om.indeed.com",
-  "pk.indeed.com",
-  "pa.indeed.com",
-  "pe.indeed.com",
-  "ph.indeed.com",
-  "pl.indeed.com",
-  "pt.indeed.com",
-  "qa.indeed.com",
-  "ro.indeed.com",
-  "sa.indeed.com",
-  "sg.indeed.com",
-  "za.indeed.com",
-  "kr.indeed.com",
-  "es.indeed.com",
-  "se.indeed.com",
-  "ch.indeed.com",
-  "tw.indeed.com",
-  "th.indeed.com",
-  "tr.indeed.com",
-  "ua.indeed.com",
-  "ae.indeed.com",
-  "uk.indeed.com",
-  "www.indeed.com",
-  "uy.indeed.com",
-  "ve.indeed.com",
-  "vn.indeed.com"
-]

First observedApr 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare read-only/open-world, and the description layers on genuinely useful behavior: the returned field set, the warning that jobKey is the only reliable dedup key for sponsored postings, and the sponsoredOnly quirk where requests exit from the domain's country (Canadian results served as sponsored). These are non-obvious traits not derivable from annotations.

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?

A single front-loaded paragraph that leads with purpose then progresses through filters, return shape, edge cases, and use cases. Dense but each clause carries information; slight overload on return-field enumeration.

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

Completeness5/5

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

No output schema exists, so the description correctly compensates by listing the returned job fields and the stable jobKey. For an 8-parameter read tool with full annotation coverage, no call-critical information is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real semantic value beyond the schema: it clarifies jobKey's dedup role and the sponsoredOnly country-domain behavior. The remoteType country-vs-city nuance largely restates the schema description.

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?

Opens with a specific verb+resource ('Searches Indeed job listings by keyword and location') and enumerates the filter scope. It also distinguishes itself from the sibling hasdata_indeed_job_getJobDetails by framing its output as URL lists to feed into the Indeed Job endpoint.

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 application contexts (job-market dashboards, hiring-trend analysis, sourcing pipelines, URL-list generation for the Job endpoint). Clear when-to-use, but no explicit exclusions or statement of when the sibling detail endpoint should be preferred instead.

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.

Resources

Need Help?