SiteCheck Jobs & Property

Indeed job search: title, company, location, salary range

jobs_indeed

Read-only

Indeed job search (US): title, company, location, salary range, job type, posting date and link for the first page of results (up to ~15 jobs) for a keyword and location, read from indeed.com's public search page through a residential proxy. Rankings and salaries are as Indeed shows them; no job descriptions. Related tools on this server, for a different need: jobs_simplyhired when you need SimplyHired job search: title, company, location, salary; jobs_payscale when you need US median pay for a job title from PayScale's public salary. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "jobs_indeed"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Job keyword, e.g. 'python' or 'nurse'
`limit`	No	How many jobs, 1 to 20 (default 10)
`location`	No	City/state or ZIP, e.g. 'Austin, TX' (optional)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond them — scraping via a residential proxy from indeed.com's public page, rankings/salaries reproduced as Indeed shows them, no job descriptions returned, and per-call pricing of $0.002 USDC via x402 with failed calls free. The one ambiguity is that the prose caps results at "up to ~15 jobs" while the limit parameter accepts 1–20, leaving the agent unsure which is authoritative.

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 dense paragraph, front-loaded with what is returned before the sibling routing and price. The sibling sentence is compressed into one line, though the pricing/payment and proxy details in the same block make it slightly breathless for a three-parameter tool.

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?

With an output schema present, the description need not detail return values, yet it still sketches the fields and, importantly, warns that no job descriptions come back. Cost, payment path, data-source mechanics, and page depth are all covered; only the ~15-vs-limit-20 discrepancy keeps it from being fully self-consistent.

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 q, limit, and location are already documented with examples, and the baseline applies. The description reinforces that the search is a keyword-plus-location lookup against Indeed's US site, which adds a little scoping meaning, but it says nothing about limit behavior or what happens without a location.

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?

"Indeed job search (US)" names the verb, the source, and the geographic scope in four words, then enumerates the returned fields (title, company, location, salary range, job type, posting date, link) and the input shape (keyword + location, first page, up to ~15 jobs). It also names the two overlapping siblings and what they do differently, so an agent can separate it from jobs_simplyhired and jobs_payscale without opening any schema.

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

Usage Guidelines5/5

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

Alternatives are named with the condition that selects them: jobs_simplyhired "when you need SimplyHired job search" and jobs_payscale "when you need US median pay for a job title." The US-only scope and first-page-only limit are stated up front, which tells the agent when this tool is insufficient.

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

All SiteCheck Jobs & Property tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?