Resume Booster Job Board

Search jobs

search_jobs

Read-onlyIdempotent

Search the live job board (postings pulled directly from employers' own hiring systems, 30-day freshness cap; board_stats carries the live totals). Returns compact job cards — including the board's own parsed pay (salaryMinAnnual/salaryMaxAnnual/salaryPeriod), experience band and minYears, so pay and seniority never have to be re-read out of prose — plus the board's honesty disclosures: exact totals when knowable (countUnavailable otherwise), filters it could not honour (ignoredFilters), words it read as filters (intentFilters), and spelling suggestions. Set agentReadyOnly=true to see only jobs the apply agent can submit to directly.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Default relevance.
`limit`	No	Rows per page, 1-60. Default 20.
`query`	No	Search terms. Supports exclusions: 'engineer -senior'.
`offset`	No	Paging offset — pass back the previous response's nextOffset.
`remote`	No	Only remote-friendly roles.
`vendor`	No	Comma list of hiring-system vendors (greenhouse, lever, ashby, …), max 8.
`country`	No	ISO-2 codes, comma-separated, max 5. E.g. 'US,GB'.
`category`	No	Comma list of category slugs (see board_stats for the live set), max 3.
`location`	No	City/state/metro, e.g. 'texas', 'NYC', 'berlin'.
`maxYears`	No	Only roles asking for at most N years of experience.
`payBasis`	No	Restrict to hourly or salaried pay.
`workMode`	No	Comma list of: remote, hybrid, onsite.
`companies`	No	Scope to specific employers: a comma list of companyToken values from job cards (or from the site's employer pages). An employer the board does not carry simply matches nothing; tokens the board drops are named in ignoredFilters.
`salaryMax`	No	Annual USD-equivalent salary ceiling.
`salaryMin`	No	Annual USD-equivalent salary floor. Note: only ~13% of postings state pay.
`department`	No	Substring match on the employer's own department/team text.
`experience`	No	Comma list of seniority bands the POSTING asks for: entry, mid, senior, expert. Rows whose band could not be read are excluded — use maxYears for the candidate's own side of the question.
`maxAgeDays`	No	Only postings from the last N days (1-30).
`postedAfter`	No	ISO-8601 instant; only postings the EMPLOYER dated after it. Undated rows fall out of this window (unlike maxAgeDays, which falls back to when the board first saw a posting), so this is the strict form of 'new'.
`hasStatedPay`	No	Only postings that state a salary (excludes the ~87% that don't).
`agentReadyOnly`	No	Only jobs the apply agent can submit to on the user's behalf.
`employmentType`	No	Comma list of: full_time, part_time, contract, temporary, internship.
`excludeAgencies`	No	Hide postings from staffing/recruiting agencies (their job cards carry agency:true). Agencies are served by default; this is an opt-in narrowing.
`includeUnstatedPay`	No	WIDENS an active salaryMin/salaryMax band to also admit postings that state no pay at all. Inert with no band set (unpriced rows are already included). The response says salaryStatedOnly when a band is narrowing without it.

Output Schema

TableJSON Schema

Name	Required	Description
`jobs`	Yes
`total`	No	Exact match count. ABSENT with countUnavailable:true when the board refuses to guess.
`hasMore`	No
`didYouMean`	No
`nextOffset`	No	Pass back as `offset` for the next page.
`excludedTerms`	No
`intentFilters`	No	Words read out of the query as filters.
`ignoredFilters`	No	Filters the board could NOT apply. Results answer a wider question than was asked.
`agenciesExcluded`	No	Row-selecting: disclosed agency inventory is hidden from this page.
`countUnavailable`	No	The board could not count this query exactly — do not report a total.
`salaryStatedOnly`	No	Row-selecting: this page excludes the ~87% of postings with no stated pay.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already mark this read-only and non-destructive, so the description's extra detail is additive, not redundant. It discloses the 30-day freshness cap, parsed pay/experience fields so prose parsing is unnecessary, and honesty mechanics (countUnavailable when totals are unknowable, ignoredFilters, intentFilters, spelling suggestions). This gives an agent a realistic model of response behavior not inferable from schema alone.

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?

The three-sentence description is dense but each clause earns its place: core purpose and source, return-card content and honesty disclosures, and the agentReadyOnly flag. It is front-loaded with the search action before going into output details, and it avoids repeating the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 24-parameter tool with no required parameters, an output schema, and read-only annotations, the description supplies the missing operational context: data freshness, sourcing, strictness of filters (ignoredFilters/intentFilters), and the agent-ready subset. Nothing an agent needs in order to decide whether to call this tool is absent.

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 baseline is 3 even with minimal parameter prose in the tool description. The description adds useful context for output fields like salaryMinAnnual/salaryMaxAnnual and agentReadyOnly, but it does not explain parameter values beyond what each schema property already says.

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?

States a specific verb, resource, and scope: 'Search the live job board', with source ('employers' own hiring systems') and a 30-day freshness cap. It also names the related sibling board_stats as the carrier of live totals, which helps an agent tell this tool apart from other board tools. The return-card and disclosure content further clarify exactly what this tool produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes the use case clear: search the live job board and get compact job cards, with an agentReadyOnly flag for direct submittable jobs. It notes that board_stats carries live totals, a useful pointer to an alternative for aggregate numbers. It does not, however, explicitly contrast search_jobs with sibling search/get_jobs/debug_search.

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

All Resume Booster Job Board 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.