Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

datasets_jobs_nearby

Find postings near a coordinate. Finds crawled job postings within radius_km of a lat/lon, nearest first. Only geocoded postings participate (the geo-enrich worker back-fills coordinates from each posting's location).

Instructions

Find postings near a coordinate. Finds crawled job postings within radius_km of a lat/lon, nearest first. Only geocoded postings participate (the geo-enrich worker back-fills coordinates from each posting's location). Open roles only by default. provider enum: greenhouse, lever, ashby, workday, smartrecruiters, workable, recruitee, rippling, personio, teamtailor, oracle, ukg, icims, eightfold, gem, pinpoint, amazon-jobs, apple-jobs, google-jobs, meta-jobs, tesla-jobs. Billing: this endpoint costs 1 credit per 10 records returned, rounded up, with a minimum of 1 (up to 10 records cost 1, a full page of 100 costs 10).

Input Schema

NameRequiredDescriptionDefault
latYesLatitude, -90..90
lonYesLongitude, -180..180
pageNoPage number, default 1
providerNoProvider filter
page_sizeNoPage size, default 20, max 100
radius_kmNoSearch radius in km, default 50, max 500
include_closedNoInclude closed/filled roles (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / provider / enum
      Added value: +[
+  "greenhouse",
+  "lever",
+  "ashby",
+  "workday",
+  "smartrecruiters",
+  "workable",
+  "recruitee",
+  "rippling",
+  "personio",
+  "teamtailor",
+  "oracle",
+  "ukg",
+  "icims",
+  "eightfold",
+  "gem",
+  "pinpoint",
+  "amazon-jobs",
+  "apple-jobs",
+  "google-jobs",
+  "meta-jobs",
+  "tesla-jobs"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / provider / description
      Previous value: -"ATS provider filter"New value: +"Provider filter"
  3. Addedv1.6.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden and does so well: it explains the geocoded-only coverage limitation (the geo-enrich back-fill), the default open-roles-only behavior, and the credit-based billing formula including the minimum and the 100-record case. What is missing is auth/permission requirements and any rate limit beyond billing.

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

Conciseness3/5

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

The behavioral sentences are front-loaded and earn their place, but the full 21-value provider enum is reproduced in prose despite being fully present in the schema, bloating the description without adding information. Trimming the enum would leave a tight, useful definition.

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 7-parameter read tool with no output schema, the description covers scope, filtering defaults, data-coverage caveats, and cost, so an agent has enough to invoke it correctly. Return format and pagination semantics are the only omissions, and they are minor given there is no output schema to explain.

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 lat/lon bounds, page defaults, page_size max, radius_km default/max and include_closed default are all already documented in the schema. The description adds only 'nearest first' ordering context and repeats the provider enum verbatim, so it stays at the baseline 3.

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 opening sentence names a specific verb and resource ('Find postings near a coordinate') and the second sentence pins down the mechanism ('within radius_km of a lat/lon, nearest first'). The geographic scoping immediately distinguishes it from keyword siblings like datasets_jobs_search and the item/facets tools, so an agent can route correctly without opening schemas.

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 discloses meaningful conditions (only geocoded postings are eligible, open roles only by default), which helps an agent predict empty results. However, it never names an alternative or states when to prefer this over datasets_jobs_search, so the when-to-use-vs-alternative guidance is only implied.

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