Pullwire

Indeed Jobs Scraper

indeed-jobs

Read-only

Search Indeed job postings by keyword, job title, company, location and posted date: title, company, rating, salary, job type, benefits, the full description and the employer’s website and size. No login, no browser. Costs 1 credit per result; failed items are free.

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": {
      "searches": "<searches>"
    },
    "name": "indeed-jobs"
  }
}

Input Schema

Name	Required	Description
`searches`	Yes	One entry per search: keywords, job title, company, location and filters.
`maxResults`	No	Stop after this many jobs in total across all searches. Empty: no extra cap.
`includeDescription`	No	Add the full job description text. Fetched in batches of 10 jobs per extra request, same price per job.
`includeCompanyDetails`	No	Add the employer’s website, domain, industry, employee range, revenue range and headquarters from its Indeed company page (one extra request per distinct company, same price per job).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld and non-destructive, so the bar is lower, and the description still adds real value: no authentication or browser session is required, and pricing is disclosed as 1 credit per result with failed items free. It does not mention the guest-pagination cap and sign-in truncation behavior, which the schema covers instead.

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 compact sentences, front-loaded with the action and source, followed by the return fields and the cost/auth notes. The long list of returned fields is dense but each item earns its place since there is no output schema.

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 nested multi-search scraper with no output schema, the description covers the essential unknowns: what is returned, that no login is needed, and the credit cost model. The remaining operational details (radius, sort, per-search caps, sign-in fallback) are fully documented in the schema, so little is missing.

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 every nested search field, including defaults, enums and the ~100-result pagination limit. The description only restates the filter dimensions at a high level, adding no syntax or format detail beyond what the schema already provides.

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?

States a specific verb and resource ('Search Indeed job postings') and enumerates the searchable dimensions plus the returned fields, so an agent knows exactly what it gets. It differentiates itself from the linkedin-jobs sibling by naming the source (Indeed), though it never explicitly contrasts the two.

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 only implied by the search-oriented framing; there is no explicit statement of when to prefer this over linkedin-jobs or other job sources, and no exclusion conditions. 'No login, no browser' hints at frictionless use but stops short of routing guidance.

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

All Pullwire 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?