ScrubShifts Healthcare Jobs

Search healthcare jobs

search_jobs

Read-only

Search live US nursing and allied-health job openings by location, role, specialty, shift, pay and requirements. Data is refreshed daily from employer career sites. Each result has a one-line summary, structured pay, a listing_url to show the person, and an apply_url that goes straight to the employer.

Input Schema

Name	Required	Description
`q`	No	Free-text words that must appear in the title, employer or location, e.g. an employer name.
`near`	No	Where the person wants to work: "City, ST", a 5-digit ZIP, or "lat,lng". Results are sorted by distance.
`role`	No	Role slug or common name, comma-separated for several: rn, lpn, cna, nurse_practitioner, crna, physical_therapist, respiratory_therapist, medical_assistant, … (see list_filters).
`sort`	No	best (default): +2 if pay is listed, -1 per week since posting, -1 per 10 miles. Or newest, pay, distance (default when near is set). Sponsored listings (sponsored: true) may appear first.
`limit`	No	Results per page, default 10, max 50.
`shift`	No	days, nights, evenings, rotating, weekends.
`state`	No	Two-letter US state code, e.g. CO. Use instead of near for a statewide search.
`offset`	No	Pagination offset; use next_offset from the previous response.
`remote`	No	Only remote / telehealth jobs.
`has_pay`	No	Only jobs that list pay.
`setting`	No	Care setting: hospital, clinic, skilled_nursing, home_health, hospice, dialysis_center, telehealth, urgent_care, school, correctional, ambulatory_surgery.
`new_grad`	No	Only jobs open to new graduates (residencies, 'new grads welcome', no experience required).
`specialty`	No	Unit or specialty, comma-separated: icu, emergency, labor_delivery, nicu, med_surg, telemetry, operating_room, oncology, psych, pediatrics, home_health, hospice, dialysis, … Common words like ER, L&D, tele, peds work.
`min_annual`	No	Minimum annual pay in USD.
`min_hourly`	No	Minimum hourly pay in USD; matches jobs whose listed range reaches it. Implies has_pay.
`posted_after`	No	Only jobs the employer posted on or after this ISO date/time.
`radius_miles`	No	Search radius around near, default 30, max 200.
`compact_license`	No	Only jobs that mention accepting a compact (multistate) nursing license.
`employment_type`	No	full_time, part_time, prn (per diem), contract, travel, temporary, internship.
`first_seen_after`	No	Only jobs that first appeared on ScrubShifts on or after this ISO time. For recurring checks, pass the previous response's data_as_of to get just the new jobs.
`posted_within_days`	No	Only jobs posted in the last N days.
`max_years_experience`	No	The person's years of experience; excludes jobs that state a higher minimum.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / sort / description

Previous value: -"best (default): +2 if pay is listed, -1 per week since posting, -1 per 10 miles. Or newest, pay, distance (default when near is set). No paid placement affects ordering."New value: +"best (default): +2 if pay is listed, -1 per week since posting, -1 per 10 miles. Or newest, pay, distance (default when near is set). Sponsored listings (sponsored: true) may appear first."

Changed4 schema fields changedOct 11, 2026

addedInput schema / properties / first_seen_after

Added value: +{
+  "description": "Only jobs that first appeared on ScrubShifts on or after this ISO time. For recurring checks, pass the previous response's data_as_of to get just the new jobs.",
+  "type": "string"
+}

addedInput schema / properties / posted_after

Added value: +{
+  "description": "Only jobs the employer posted on or after this ISO date/time.",
+  "type": "string"
+}

changedInput schema / properties / sort / description

Previous value: -"newest (default), pay, or distance (default when near is set)."New value: +"best (default): +2 if pay is listed, -1 per week since posting, -1 per 10 miles. Or newest, pay, distance (default when near is set). No paid placement affects ordering."

changedInput schema / properties / sort / enum

Previous value: -[
-  "newest",
-  "pay",
-  "distance"
-]New value: +[
+  "best",
+  "newest",
+  "pay",
+  "distance"
+]

First observedOct 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's added value is the provenance and freshness ('refreshed daily from employer career sites') plus the return shape. Distinguishing listing_url (to show the person) from apply_url (straight to the employer) is genuinely useful behavioral context absent from annotations and 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.

Conciseness5/5

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

Two sentences with no filler: the first front-loads what is searched and over what facets, the second delivers freshness and result structure. Every clause earns its place, and nothing is restated from the 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 22-parameter tool with no output schema, the description does the important extra work of describing the return fields and data freshness. It leaves pagination behavior and sort-default interaction to the schema, which is a minor gap given the 100% schema coverage.

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%, with detailed per-parameter docs including the sort scoring formula, defaults, and enum values, so the schema carries the semantic load. The description only gestures at the facets generally and adds no parameter-level detail beyond what the schema already states, making the baseline 3 correct.

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 opens with a specific verb and resource ('Search live US nursing and allied-health job openings') and enumerates the searchable facets (location, role, specialty, shift, pay, requirements). Because it describes plural results ('Each result has...'), it is clearly distinguishable from the sibling get_job, which returns a single posting.

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: the domain (US nursing/allied health) and the mention of daily refresh suggest when this tool applies, but there is no explicit when-to-use versus get_job, list_filters, or get_pay_benchmarks guidance, and no stated exclusions. An agent must infer routing from the sibling names.

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

All ScrubShifts Healthcare Jobs 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.

Search healthcare jobs

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources