Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

indeed_search

Search Indeed job postings by keyword and location, then sort by relevance or date and filter by posting age or radius.

Instructions

Indeed job search. Searches Indeed job postings by keyword and location. sort enum: relevance (default), date.

Input 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

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no pagination limits, no result-count behavior, no rate limits, no auth requirements. The only behavioral hint is that `sort` defaults to relevance, which is already in the schema.

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?

Three short clauses, front-loaded with the verb and resource. Efficient and free of filler, though the trailing sort-enum note is redundant with the schema.

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?

With no annotations and no output schema, the description should compensate on return shape and scoping (e.g. result fields, pagination), but it leaves both unaddressed. For a 6-parameter search tool in a dense job-board sibling cluster, this is under-specified.

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 six parameters. The description only restates the `sort` enum and its default, adding no meaning beyond structured data. Baseline 3 applies.

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 ('Searches Indeed job postings by keyword and location'), which is clear and actionable. However, it does not distinguish itself from the sibling indeed_job or indeed_locations_suggest, so an agent must rely on the name to route correctly.

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 when-to-use guidance and no alternatives named. The description never explains when to pick this over indeed_job (detail) or indeed_locations_suggest, which are the obvious siblings an agent would otherwise confuse it with.

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