Outscraper MCP

Official

Overview Schema Source Related Servers Discussions Admin

Indeed Search

indeed_search

Search Indeed for job postings by providing one or more queries. Retrieve structured job data with configurable limits, fields, and execution modes for flexible integration.

Instructions

Search Indeed with the documented /indeed-search endpoint.

Input Schema

TableJSON Schema

Name	Required	Description
`async`	No	Deprecated compatibility flag. Prefer execution_mode.
`limit`	No	Maximum results.
`query`	Yes	One or more Indeed search queries.
`fields`	No	Specific fields to return.
`webhook`	No	Optional webhook URL for async completion.
`enrichment`	No	Optional documented enrichments.
`execution_mode`	No	Execution strategy. Use auto to let the MCP server choose between sync and async.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`meta`	Yes
`async`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.2.5Sep 23, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedv0.2.3Aug 1, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden. It only states that it searches via an endpoint, giving no information about execution modes, rate limits, data handling, or side effects. This is minimal and uninformative for a tool that has async capabilities and enrichment options.

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

Conciseness2/5

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

The description is extremely short (one sentence) but it's under-specification rather than effective conciseness. It repeats the tool name and adds no structural benefit or front-loaded key information. It fails to convey any actionable details.

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

Completeness2/5

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

Given the tool has 7 parameters, an output schema, and many sibling alternatives, the description is severely incomplete. It doesn't explain return structure, execution behavior, or selection criteria. Even though output schema exists, an agent lacks enough context to know when to call this tool correctly.

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?

The schema provides 100% description coverage for all 7 parameters, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already documents. It doesn't compensate or elaborate on any parameter semantics.

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

Purpose4/5

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

The description states a clear verb+resource: 'Search Indeed'. It clearly identifies the target platform, distinguishing it from other search tools like google_search or yellowpages_search. However, it doesn't mention any scope or specific capabilities beyond the generic search, so it's not fully differentiated from similar siblings.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus the many sibling search tools. It doesn't mention any prerequisites, context, or exclusions. An agent cannot infer when Indeed is the appropriate choice.

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