Nomado24 Remote Jobs

Search remote jobs

search_jobs

Read-onlyIdempotent

Search nomado24's remote/hybrid job board. Read-only, free access. No blanket content licence; retain attribution and respect third-party rights (see structuredContent.attribution). Answers over one of two contracts, chosen by the arguments you send. Send only q/language/page/per_page and you get the legacy v1 result shape with page-based paging. Send any structured filter (country, applicant_region, work_arrangement, employment_type, seniority, skills, salary_min/max, published_after, verified_after, source, company, sort, include_total) or a cursor and you get the v2 contract: richer job objects, per-posting provenance (salaryOrigin, firstSeenAt, lastVerifiedAt, verification.method, updatedAt), a corpus changeWatermark, a snapshotId and keyset paging via pagination.nextCursor. The two are mutually exclusive: page plus a structured filter is refused rather than silently resolved. Structured results omit per-field dataOrigin; call get_job for provenance. Copied posting text and external application URLs are withheld by default unless separately documented redistribution permission exists. A filter nomado24 cannot answer honestly is refused with the reason, never answered with the unfiltered corpus. Structured pagination.total is currently null (totalRelation 'not_computed') for every query, because a current-text on-site-only serving gate cannot be counted accurately by the database. A null total is deliberate, not an error.

Input Schema

Name	Required	Description
`q`	No	Free-text search over job title/company/tags
`page`	No	1-based page number, default 1
`sort`	No	One of published_desc, verified_desc, salary_asc, salary_desc. Default published_desc
`cursor`	No	Continuation cursor from pagination.nextCursor. Send it ALONE (with per_page at most), never alongside filters: the cursor already carries the filter set it traverses
`skills`	No	Skill slugs, lowercase kebab-case (react, node-js)
`source`	No	Feed/source ids, lowercase kebab-case
`company`	No	Company name, exact match, case-insensitive. Aggregated postings carry no verified employer identity
`country`	No	Where the ROLE sits, ISO 3166-1 alpha-2 uppercase (DE, US)
`language`	No	Filter by job content language
`per_page`	No	Results per page, 1-25, default 20
`seniority`	No	Seniority. 'unknown' means the field is absent in the response, not a stored value
`salary_max`	No	Upper bound in normalized ANNUAL EUR (gross)
`salary_min`	No	Lower bound in normalized ANNUAL EUR (gross). Matches jobs whose salary interval overlaps it
`skills_match`	No	How to combine skills. Requires skills
`include_total`	No	Requested total mode (none, estimated, exact). Totals are currently withheld for every structured search: a current-text on-site-only serving gate is not visible to the database count, even without a named filter. The response reports total: null and totalRelation: 'not_computed' for all three modes.
`verified_after`	No	RFC 3339 date-time. Compares against the SAME value the response reports as lastVerifiedAt
`employment_type`	No	Employment type. 'unknown' means the field is absent in the response, not a stored value
`published_after`	No	RFC 3339 date-time, e.g. 2026-08-01T00:00:00Z
`salary_currency`	No	ISO 4217. Only EUR: every salary is normalized to EUR at ingest and no conversion is performed
`applicant_region`	No	Where a CANDIDATE may be: WORLDWIDE, EU or an ISO 3166-1 alpha-2 code. EEA/DACH/EMEA are refused, nomado24 does not classify them
`work_arrangement`	No	Work arrangement. The board serves remote and hybrid postings only, so these are the only two values

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedInput schema / properties / include_total / description

Previous value: -"Whether to compute a total. 'exact' returns a number only when the database saw the whole predicate. With a post-projection filter active (skills, seniority, salary_min/salary_max, employment_type=unknown) the total is withheld: total is null and totalRelation is 'not_computed', because the base count would answer a different question than the one asked. Only at the count ceiling does 'exact' downgrade to 'estimated'."New value: +"Requested total mode (none, estimated, exact). Totals are currently withheld for every structured search: a current-text on-site-only serving gate is not visible to the database count, even without a named filter. The response reports total: null and totalRelation: 'not_computed' for all three modes."

Changed4 schema fields changedAug 26, 2026

changedInput schema / properties / include_total / description

Previous value: -"Whether to compute a total. 'exact' downgrades itself to 'estimated' when a post-projection filter is active or the count ceiling is hit"New value: +"Whether to compute a total. 'exact' returns a number only when the database saw the whole predicate. With a post-projection filter active (skills, seniority, salary_min/salary_max, employment_type=unknown) the total is withheld: total is null and totalRelation is 'not_computed', because the base count would answer a different question than the one asked. Only at the count ceiling does 'exact' downgrade to 'estimated'."

changedInput schema / properties / work_arrangement / description

Previous value: -"Work arrangement. 'unknown' means the field is absent in the response, not a stored value"New value: +"Work arrangement. The board serves remote and hybrid postings only, so these are the only two values"

changedInput schema / properties / work_arrangement / items / enum

Previous value: -[
-  "remote",
-  "hybrid",
-  "remote_optional",
-  "unknown"
-]New value: +[
+  "remote",
+  "hybrid"
+]

changedInput schema / properties / work_arrangement / maxItems
```
Previous value: -4New value: +2
```

Changed17 schema fields changedAug 26, 2026

addedInput schema / properties / applicant_region

Added value: +{
+  "description": "Where a CANDIDATE may be: WORLDWIDE, EU or an ISO 3166-1 alpha-2 code. EEA/DACH/EMEA are refused, nomado24 does not classify them",
+  "items": {
+    "maxLength": 16,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / company

Added value: +{
+  "description": "Company name, exact match, case-insensitive. Aggregated postings carry no verified employer identity",
+  "items": {
+    "maxLength": 128,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

addedInput schema / properties / country

Added value: +{
+  "description": "Where the ROLE sits, ISO 3166-1 alpha-2 uppercase (DE, US)",
+  "items": {
+    "maxLength": 8,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / cursor

Added value: +{
+  "description": "Continuation cursor from pagination.nextCursor. Send it ALONE (with per_page at most), never alongside filters: the cursor already carries the filter set it traverses",
+  "maxLength": 4096,
+  "type": "string"
+}

addedInput schema / properties / employment_type

Added value: +{
+  "description": "Employment type. 'unknown' means the field is absent in the response, not a stored value",
+  "items": {
+    "enum": [
+      "full_time",
+      "part_time",
+      "contract",
+      "freelance",
+      "temporary",
+      "internship",
+      "working_student",
+      "apprenticeship",
+      "minijob",
+      "volunteer",
+      "other",
+      "unknown"
+    ],
+    "type": "string"
+  },
+  "maxItems": 12,
+  "type": "array"
+}

addedInput schema / properties / include_total

Added value: +{
+  "description": "Whether to compute a total. 'exact' downgrades itself to 'estimated' when a post-projection filter is active or the count ceiling is hit",
+  "enum": [
+    "none",
+    "estimated",
+    "exact"
+  ],
+  "type": "string"
+}

addedInput schema / properties / published_after

Added value: +{
+  "description": "RFC 3339 date-time, e.g. 2026-08-01T00:00:00Z",
+  "maxLength": 64,
+  "type": "string"
+}

addedInput schema / properties / salary_currency

Added value: +{
+  "description": "ISO 4217. Only EUR: every salary is normalized to EUR at ingest and no conversion is performed",
+  "maxLength": 8,
+  "type": "string"
+}

addedInput schema / properties / salary_max

Added value: +{
+  "description": "Upper bound in normalized ANNUAL EUR (gross)",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / salary_min

Added value: +{
+  "description": "Lower bound in normalized ANNUAL EUR (gross). Matches jobs whose salary interval overlaps it",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / seniority

Added value: +{
+  "description": "Seniority. 'unknown' means the field is absent in the response, not a stored value",
+  "items": {
+    "enum": [
+      "student",
+      "entry",
+      "junior",
+      "mid",
+      "senior",
+      "lead",
+      "manager",
+      "director",
+      "executive",
+      "unknown"
+    ],
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

addedInput schema / properties / skills

Added value: +{
+  "description": "Skill slugs, lowercase kebab-case (react, node-js)",
+  "items": {
+    "maxLength": 64,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / skills_match

Added value: +{
+  "description": "How to combine skills. Requires skills",
+  "enum": [
+    "any",
+    "all"
+  ],
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "One of published_desc, verified_desc, salary_asc, salary_desc. Default published_desc",
+  "maxLength": 32,
+  "type": "string"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "Feed/source ids, lowercase kebab-case",
+  "items": {
+    "maxLength": 64,
+    "type": "string"
+  },
+  "maxItems": 20,
+  "type": "array"
+}

addedInput schema / properties / verified_after

Added value: +{
+  "description": "RFC 3339 date-time. Compares against the SAME value the response reports as lastVerifiedAt",
+  "maxLength": 64,
+  "type": "string"
+}

addedInput schema / properties / work_arrangement

Added value: +{
+  "description": "Work arrangement. 'unknown' means the field is absent in the response, not a stored value",
+  "items": {
+    "enum": [
+      "remote",
+      "hybrid",
+      "remote_optional",
+      "unknown"
+    ],
+    "type": "string"
+  },
+  "maxItems": 4,
+  "type": "array"
+}

Changed1 schema field changedAug 24, 2026
- changedInput schema / properties / per_page / maximum
```
Previous value: -9007199254740991New value: +25
```
First observedAug 2, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnly and idempotent annotations, the description discloses free access, attribution/licence obligations, withheld redistribution content, refusal behavior for unanswerable filters, and the deliberate null total. These are substantial behavioral traits an agent would not know from annotations or 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 description is dense but front-loaded with purpose and contract selection, then layers on provenance, withholding, refusal, and pagination caveats. Every sentence carries operational meaning for a 21-parameter search tool, so the length is justified rather than wasteful.

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?

With no output schema and a large parameter surface, the description supplies the missing context: two response contracts, provenance fields, cursor behavior, total semantics, refusal behavior, and attribution obligations. An agent has enough information to choose arguments and interpret the response contract correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema description coverage is already 100%, the description adds contract-level meaning that the schema does not: q/language/page/per_page alone yields v1, any structured filter or cursor yields v2, and page plus filter is refused. It also clarifies that structured results omit per-field dataOrigin and that total is intentionally null.

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 first sentence states a specific verb and resource: search nomado24's remote/hybrid job board. It clearly distinguishes this search tool from sibling tools get_job and get_job_statistics, which serve lookup and aggregate statistics rather than search.

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

Usage Guidelines5/5

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

The description explicitly explains which argument combinations select the legacy v1 versus v2 contract, that page plus structured filters is refused, and that cursor must be sent alone. It also directs agents to get_job for provenance, giving a clear alternative when per-field dataOrigin is needed.

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

All Nomado24 Remote 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.

Resources

Need Help?