RadarJobs

Inspect one current contract technology job using its Radar UUID. Active accounts can read current inventory; exploration accounts can read only jobs in their own visible personalized preview. The account identity always comes from OAuth, never from a tool argument. Returns the actual source posting URL and the separate enriched RadarJobs detail URL. Use this tool only when the user asks about one known job without a complete job object from a search or recommendation response. Never call it to verify or enrich jobs already returned by search_contract_jobs in the same turn. Treat resolved engagement_models as authoritative; do not add a contract-type caveat unless engagement_resolution.status is unresolved.

Return an active connected account's complete current personalized RadarJobs recommendation set, up to 20 jobs, in ranked order. Exploration accounts receive the same bounded five-job preview as the RadarJobs website. This reads the same cached recommendation set as RadarJobs and refreshes it only when current-inventory checks hide stale rows. It never uploads a resume, creates profile defaults, or starts checkout. Every recommendation is presentation-complete with pay, location, resolved contract type, supporting evidence, source, verification time, source_posting_url, and radarjobs_url. Present the response immediately; never call get_contract_job to re-fetch or verify these jobs.

Search up to five current contract technology jobs for the connected RadarJobs account. Full search requires the account's existing active paid-equivalent access; this tool never starts checkout. Put the user's ordinary role wording in role; RadarJobs resolves it deterministically without a vocabulary lookup. Use 1099/c2c/w2_contract for engagement. When the user explicitly pairs freelance with 1099 or independent-contractor work, use the supported 1099 value; never send an unsupported freelance enum. title_contains matches titles, not descriptions. Exact is the default; closest may relax only the title when a role taxonomy filter is also supplied. Call this tool at most once per user request. A response with zero or fewer than the requested limit is complete, not a reason to retry. Never change filters or search again until the user explicitly chooses a constraint to broaden in a later message. Each result includes the actual source_posting_url and a separate enriched radarjobs_url. When links are requested, return both and label them clearly. Every search item already includes pay, location, resolved contract type, supporting evidence, source, verification time, and both links; do not call get_contract_job to re-fetch or verify any search result. Treat resolved engagement_models as authoritative; do not add a contract-type caveat unless engagement_resolution.status is unresolved.