Skip to main content
Glama

Search jobs

search_jobs
Read-onlyIdempotent

Search Jobven job postings with the filters of GET /v1/public/jobs. Returns 10 jobs by default (at most 25) with a plain-text excerpt of each description; get_job has the full text. Pass nextCursor back as cursor, with the same filters, for the next page. Each job returned counts toward the monthly allowance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoSearch job titles by whole word. Words are ANDed in any order; "double quotes" match an exact phrase, OR matches either side, and a leading - excludes a word. Case-insensitive. Does not search descriptions (see descriptionQuery).
atsNoPlatform the posting is published on, any of, e.g. ["workday", "greenhouse"]
cityNoCity, comma-separated; case and accents are ignored
limitNoJobs per page, default 10, at most 25
orderNoDefault DESC
stateNoState, province or region, comma-separated: full name ("Ontario") or, for the US and Canada, the postal code ("ON")
cursorNonextCursor from the previous search_jobs result, same filters
skillsNoSkills, any of (up to 10), e.g. ["typescript", "react"]
sortByNoSort field (default postedAt)
statusNo"active" (the default) or "closed"
countryNoISO 3166-1 alpha-2 country code, e.g. "US", "CA", "GB". "XX" matches jobs with no location at all.
industryNoIndustries, any of (up to 10)
languageNoRequired spoken language, ISO 639-1 code, e.g. "fr"
locationNoFree-text location: city, region or country
maxSalaryNoMaximum yearly starting pay, as minSalary
minSalaryNoMinimum yearly pay; hourly, daily, weekly and monthly pay is compared per year. In each job's own currency unless salaryCurrency is set
remoteTypeNoRemote type, any of
closedAfterNoClosed at or after (Unix seconds), by closedAt; requires status "closed"
listedAfterNoListed at or after (Unix seconds), by listedAt: for incremental sync
postedAfterNoPosted at or after (Unix seconds)
includeTotalNoAlso count every match (slower)
postedBeforeNoPosted before (Unix seconds)
hasRelocationNotrue: postings that offer relocation help; false: postings that say they do not
employmentTypeNoEmployment type, any of
salaryCurrencyNoISO 4217 currency code of the salary, e.g. USD, EUR, PLN
experienceLevelNoExperience level, any of
descriptionQueryNoSearch job descriptions for a whole-word phrase, matched literally, case-insensitive. Slower than the other filters; pair it with postedAfter.
hasVisaSponsorshipNotrue: postings that offer visa sponsorship; false: postings that say they do not

Output Schema

NameRequiredDescriptionDefault
jobsYes
totalNo
hasMoreYes
requestYesThe REST call this result came from. curl reads the key from $JOBVEN_API_KEY.
nextCursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / closedAfter
      Added value: +{
      +  "description": "Closed at or after (Unix seconds), by closedAt; requires status \"closed\"",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / ats
      Added value: +{
      +  "description": "Platform the posting is published on, any of, e.g. [\"workday\", \"greenhouse\"]",
      +  "items": {
      +    "enum": [
      +      "adp",
      +      "appvault",
      +      "ashby",
      +      "avature",
      +      "bamboohr",
      +      "beesite",
      +      "brassring",
      +      "breezy",
      +      "catsone",
      +      "ceipal",
      +      "clearcompany",
      +      "collage",
      +      "comeet",
      +      "cornerstone",
      +      "darwinbox",
      +      "dayforce",
      +      "deel",
      +      "directemployers",
      +      "dover",
      +      "easyapply",
      +      "eightfold",
      +      "gem",
      +      "getnoticed",
      +      "greenhouse",
      +      "hibob",
      +      "hireology",
      +      "hrsmart",
      +      "icims",
      +      "jazzhr",
      +      "jobdiva",
      +      "jobvite",
      +      "join",
      +      "kula",
      +      "lever",
      +      "njoyn",
      +      "oracle",
      +      "paradox",
      +      "paycor",
      +      "paylocity",
      +      "personio",
      +      "phenom",
      +      "pinpoint",
      +      "prevue",
      +      "radancy",
      +      "recruitee",
      +      "rippling",
      +      "smartrecruiters",
      +      "successfactors",
      +      "talentnest",
      +      "taleo",
      +      "teamtailor",
      +      "ukg",
      +      "workable",
      +      "workday"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "minItems": 1,
      +  "type": "array"
      +}
  3. Changed3 schema fields changed
    • changedInput schema / properties / maxSalary / description
      Previous value: -"Maximum stated salary"New value: +"Maximum yearly starting pay, as minSalary"
    • changedInput schema / properties / minSalary / description
      Previous value: -"Minimum stated salary"New value: +"Minimum yearly pay; hourly, daily, weekly and monthly pay is compared per year. In each job's own currency unless salaryCurrency is set"
    • addedInput schema / properties / salaryCurrency
      Added value: +{
      +  "description": "ISO 4217 currency code of the salary, e.g. USD, EUR, PLN",
      +  "pattern": "^[A-Za-z]{3}$",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing pagination semantics, that descriptions come back truncated as plain-text excerpts, and the cost model ("Each job returned counts toward the monthly allowance"). The quota disclosure is a behavioral trait an agent cannot infer from readOnlyHint/idempotentHint and materially changes how it should size limit and page count.

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?

Four short sentences, front-loaded with purpose then page size, excerpt truncation, pagination, and cost. The "Returns 10 jobs by default (at most 25)" clause partly duplicates the limit parameter description, and the raw endpoint path adds little for an agent, but there is no filler.

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 28-parameter search tool with an output schema and rich annotations, the description covers the operational essentials an agent needs: result size, truncation, cursor continuation, and quota impact. It leaves filter interaction semantics (how multiple filters combine, enum-array OR behavior) to the schema, which is a reasonable division given 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%, so the parameter semantics are already fully documented in the schema; the description only restates the limit default/max and the cursor round-trip, both of which appear in the schema descriptions. Baseline 3 applies since the description adds no filter-combination or cross-parameter semantics.

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 and resource ("Search Jobven job postings") and scopes it by naming the underlying filter set of GET /v1/public/jobs. It also distinguishes itself from the sibling get_job by noting it returns only a plain-text excerpt rather than full descriptions.

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?

Gives a concrete routing rule (use get_job for full text) and explicit continuation instructions (pass nextCursor back as cursor with the same filters). It does not state exclusions such as when a narrower sibling like search_companies or a direct get_job lookup would be preferable to a broad search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources