Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indeed_search

Searches Indeed job postings by keywords and location, letting users narrow results by radius, posting age, page, and sort order.

Instructions

Indeed job search. Searches Indeed job postings by keyword and location. Primary transport is Indeed's own credential-free GraphQL API; a page 1, unfiltered-by-date request uses it directly. Requesting page 2+ or the fromage filter (not yet expressible over the primary transport) uses the original web-page transport instead, with the same normalized response shape either way. sort enum: relevance (default), date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lNoLocation (city, state, or zip)
qYesSearch keywords
pageNoPage number, 1-based, defaults to 1
sortNoSort order: relevance, date
radiusNoSearch radius in miles
fromageNoOnly jobs posted within this many days

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "date"
+]
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full transparency burden and does so exceptionally. It discloses that the primary transport is credential-free, that certain requests fall back to a web-page transport, that the response shape is normalized across both, and that fromage is not yet expressible on the primary transport.

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 compact and front-loaded, with the purpose in the second sentence and transport/parameter details following efficiently. The opening fragment 'Indeed job search.' is redundant with the tool name, preventing a perfect score.

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 6-parameter search tool with no output schema and no annotations, the description is unusually thorough: it covers core semantics, transport switching, sort default, and the fromage limitation. It still leaves the normalized response shape unspecified and does not mention rate limits or result-size caveats.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already describes all 6 parameters, so the baseline is 3. The description adds meaningful value beyond the schema by noting the sort default ('relevance'), the transport-routing implications of page and fromage, and the consistent response shape across transports.

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?

The description states a specific verb and resource: 'Searches Indeed job postings by keyword and location.' This clearly distinguishes it from sibling tools like indeed_job (single posting fetch) and indeed_locations_suggest (location autocomplete), even without naming them.

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?

It provides clear behavioral context for choosing parameters: page 1 unfiltered uses the GraphQL transport, while page 2+ or fromage triggers the web-page transport, with a normalized response either way. However, it never explicitly tells the agent when to use this search tool versus siblings like indeed_job or google_jobs_search; usage is implied rather than stated.

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

Deploy Server

Other Tools