webdata-tools-mcp

Search Indeed jobs

search_indeed_jobs

Read-onlyIdempotent

Find Indeed jobs by keyword and location in 9 countries, returning titles, companies, salaries, job types, benefits, skills, and apply links.

Instructions

Search Indeed job listings by keyword and location in 9 countries (us, uk, ca, au, ie, de, fr, nl, sg): title, company, location, salary, job type, benefits, skills and apply link. Runs the Apify Actor tacps126/indeed-jobs on your Apify account (about $0.003 per job; spend per call is capped at $0.5).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Job title, skill or company, e.g. "react developer".
`country`	No	Indeed country site.	us
`job_type`	No	Only this employment type.
`location`	No	City, state, postcode or "Remote". Empty = whole country.
`max_items`	No	Maximum results to return (default 30, max 500). Cost scales with this.
`extra_input`	No	Advanced: extra Actor input fields, merged over the defaults.
`date_posted_days`	No	Only jobs posted in the last N days.

Output Schema

TableJSON Schema

Name	Required	Description
`tool`	Yes	Name of the tool that produced the result.
`count`	Yes	Number of records the Actor returned.
`items`	Yes	The records. Long text fields are shortened to 600 characters.
`shown`	Yes	Number of records included in `items` (can be lower than count when the result is long).
`truncated`	Yes	True when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.1.1Oct 17, 2026

addedInput schema / properties / job_type / description
```
Added value: +"Only this employment type."
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "count": {
+      "description": "Number of records the Actor returned.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "items": {
+      "description": "The records. Long text fields are shortened to 600 characters.",
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "shown": {
+      "description": "Number of records included in `items` (can be lower than count when the result is long).",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "tool": {
+      "description": "Name of the tool that produced the result.",
+      "type": "string"
+    },
+    "truncated": {
+      "description": "True when records were left out to keep the result short; ask for fewer items.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "tool",
+    "count",
+    "shown",
+    "truncated",
+    "items"
+  ],
+  "type": "object"
+}

First observedv0.1.0Oct 17, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the description doesn't need to restate safety. It does add meaningful non-obvious behavior: it runs a specific Apify Actor on the user's own Apify account, costs about $0.003 per job, and caps spend per call at $0.5. That cost/credential context is valuable beyond the annotations; it stops short of describing return shape or pagination, but the output schema exists.

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 sentences, front-loaded with the core purpose and field list, then operational context (Actor, cost, cap). No filler, though the long parenthetical could be trimmed slightly.

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 read-only search over 7 params with full schema coverage and an output schema, the description covers purpose, scope, return fields, cost and spend cap. The only meaningful omission is guidance on choosing it over sibling job tools and any account/auth prerequisite.

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 coverage is 100%, so every parameter is already documented with types, enums and defaults, setting the baseline at 3. The description adds little parameter-level meaning beyond confirming keyword/location search and the country list; it does not explain how max_items interacts with the $0.5 cap, which would have been useful.

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 (Search) and resource (Indeed job listings) plus the exact scope: by keyword and location across nine named countries, and enumerates the fields returned. An agent can distinguish it from siblings like find_hiring_companies or get_company_jobs without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied by the query/location framing, but the description never states when to pick this over sibling job tools (find_hiring_companies, get_company_jobs) or any prerequisites such as needing an Apify account/API key. No exclusions are given.

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

Deploy Server