Relomote

Search jobs

search_jobs

Read-onlyIdempotent

Search live job listings on Relomote, collected from company career pages. board "remote" (default) finds remote and hybrid jobs a person can do from a given country, region or anywhere in the world; for a country it also includes jobs open to its whole region and jobs open worldwide, since those are open from there too. board "relocation" finds jobs abroad that offer relocation support or visa sponsorship; there the location is where the job moves the person to. Returns at most 10 jobs per call, newest first, each with a link to its Relomote page, where the person reads the full listing and applies. A search returns at most 3 pages.

Input Schema

Name	Required	Description
`page`	No
`board`	No	"remote" (default) or "relocation" (relocation support or visa sponsorship).
`limit`	No
`query`	No	Job title or keywords, e.g. "customer support", "data analyst", "react developer". Omit to list the newest jobs for the filters.
`category`	No	Job category.
`location`	No	A country ("Nigeria", "Philippines", "DE"), a region (Africa, Asia, Europe, Latin America, Middle East, North America, Oceania) or "worldwide" (remote board only: jobs open from anywhere).
`visa_sponsorship`	No	Only jobs that sponsor a work visa. Implies the relocation board.

Output Schema

Name	Required	Description
`jobs`	Yes
`note`	No	Set when the search was reinterpreted (a typo fixed, a place read as a location).
`page`	Yes
`board`	Yes
`total`	Yes	Jobs matching the search on Relomote.
`has_more`	Yes
`see_all_url`	Yes	The same search on relomote.com.
`total_is_lower_bound`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 8, 2026

addedOutput schema / properties / jobs / items / properties / logo_url

Added value: +{
+  "description": "The company's logo, a 128px image.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedOct 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish the read-only, idempotent, non-open-world safety profile, so the burden is lighter. The description adds genuinely non-obvious behavior: results are newest-first, capped at 10 per call, a search spans at most 3 pages, and each hit is a link rather than the full listing.

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 with the core purpose, then board semantics, then output shape and pagination caps. It is dense but each sentence carries distinct information; the country/region/worldwide explanation is slightly verbose but justified by the non-obvious filtering rule.

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?

Output schema exists, so return structure need not be re-explained, yet the description still covers ordering, per-call cap, and total page limit. Remaining gaps are minor: no explicit routing to get_job for full listing detail, and no note on what happens when page exceeds 3.

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 71% and the description meaningfully extends it — board semantics, what 'location' means on each board, that 'worldwide' applies to the remote board only, and that visa_sponsorship implies the relocation board. Query and category semantics are left to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search live job listings on Relomote') plus the data provenance ('collected from company career pages'). It distinguishes the two boards clearly, and the mention that results link to a Relomote page where the listing is read implies the boundary with the get_job sibling, though that sibling is never named outright.

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 real selection logic between the two board values, including the subtle case that a country search also surfaces jobs open to its region and worldwide. It stops short of explicit when-not guidance (e.g. when to omit query, or when to call get_job instead for full listing details).

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

All Relomote 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?