Nomado24 Remote Jobs

Search remote jobs

search_jobs

Read-onlyIdempotent

Search nomado24's remote/hybrid job board. Read-only, free, attribution required (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 the posting body and the per-field dataOrigin to stay cheap to read; call get_job for those. 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

TableJSON 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

A4.8/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial context beyond them: attribution is required, refusals are explicit and reasoned, structured results deliberately omit body and dataOrigin, and pagination.total is intentionally null ('not an error'). These are behaviors an agent could not infer from the annotations or schema.

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?

Front-loaded and dense but justified for a 21-parameter dual-contract tool; every clause carries routing or caveat information. Slight deduction because the null-total explanation is repeated almost verbatim in the include_total schema description and again in the description's closing sentence.

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, 21 params and dual-contract behavior, the description still covers contract selection, paging mechanics (page vs cursor), field omissions, refusal semantics, and the deliberate null total. Nothing an agent needs to call this correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema cannot: it groups the 21 params into two mutually exclusive contracts and explains the page-plus-filter refusal rule. It does not restate individual param formats, but the contract-level semantics are the important addition.

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?

Opens with a specific verb+resource ('Search nomado24's remote/hybrid job board') and immediately differentiates itself from the sibling get_job by naming what get_job is needed for (posting body, per-field dataOrigin). An agent can tell exactly what this tool returns and when a sibling is required.

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?

Gives explicit routing rules: which argument sets select the v1 vs v2 contract, that the two are mutually exclusive and refused rather than silently resolved, that cursor must travel alone, and that unanswerable filters are refused rather than degraded. This is a genuinely complete when/how-to-call guide.

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?