webdata-tools-mcp

Search Indeed jobs

search_indeed_jobs

Read-onlyIdempotent

Search Indeed job listings by keyword, location, and filters across nine countries to retrieve structured job details (title, company, salary, benefits, apply link) for hiring or market research.

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, apply link and (with details) the full job description. 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

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.
`include_details`	No	Add each job's full description. Off = search-card summary only.
`date_posted_days`	No	Only jobs posted in the last N days.

Output 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.

Changed1 schema field changedv0.10.1Oct 23, 2026

addedInput schema / properties / include_details

Added value: +{
+  "default": true,
+  "description": "Add each job's full description. Off = search-card summary only.",
+  "type": "boolean"
+}

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

A4/5.0

Behavior4/5

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

Annotations already establish read-only, open-world, idempotent, and non-destructive behavior. The description adds meaningful operational context beyond annotations: it runs the named Apify Actor on the user's account, costs about $0.003 per job, and caps spend at $0.5 per call.

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?

The description is front-loaded with the core search action and scope, then adds cost details. It is dense but largely free of filler, though the enumerated return fields are somewhat lengthy given the presence of an output schema.

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?

For an eight-parameter search tool with full schema coverage, rich annotations, and an output schema, the description supplies the key missing operational context: supported countries, return-field scope, detail behavior, and cost bounds. Nothing essential for correct invocation appears absent.

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 the schema already documents all parameters, including enums and defaults. The description reinforces country coverage and the include_details behavior, but mostly repeats or lightly contextualizes what the schema already provides.

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 ('Search Indeed job listings') and scopes it by keyword, location, and nine country sites. The Indeed-specific framing distinguishes it from sibling job-search tools such as search_tech_jobs, search_naukri_jobs, and get_company_jobs.

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?

The description makes the intended use clear through its keyword/location and country-site scope, but it does not explicitly say when to choose this over sibling job-search tools or when not to use it. Usage is implied rather than guided.

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

Deploy Server