Ocean of Jobs

Search jobs

search_jobs

Read-onlyIdempotent

Search open jobs on Ocean of Jobs. Give at least one of query, company, city or country (IL for Israel; most listings are in the US). Returns up to 25 jobs per call, best match first when there is a query, newest first otherwise, with the total number of matches. Every job includes its lifetime (days listed, first and last seen) and two links: url, the Ocean of Jobs page, to show first, and apply_url, the employer's page.

How to search well:

Put one or two core title or skill words in query, such as "backend", "python" or "devops", and use the filters for place, seniority and dates. Every word in query must match, so a long description of the person returns little or nothing.
Search once. If that gives relevant candidates, do not search again for synonyms. If it gives nothing useful, change or broaden query once, keeping the same filters.
Across searches, treat the same id or the same apply_url as one job.
Open only the strongest few candidates with get_job, and read their descriptions for seniority, required skills and where the job can be done from before ranking them.
Give the number of recommendations asked for when enough jobs fit, and say so when fewer do.
Never call a listing reposted because of its age. Use lifetime.reappeared_at, and say when the tracked history is too short to tell.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City name, e.g. Tel Aviv.
`limit`	No
`query`	No	Words to search titles, companies, locations and descriptions, skills included, e.g. "kubernetes go". Quotes keep a phrase together.
`offset`	No
`company`	No	A company domain such as wix.com, or a name, which is looked up.
`country`	No	Two-letter country code, e.g. IL or US.
`seniority`	No
`workplace`	No
`salary_min`	No	Lowest monthly gross salary in shekels.
`max_age_days`	No	Only jobs posted within this many days.

Output Schema

TableJSON Schema

Name	Required	Description
`jobs`	Yes
`more`	Yes
`total`	Yes	Every match, not only this page.
`offset`	Yes
`duplicates_folded`	Yes	Rows on this page that were the same posting as another, folded into it.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, but the description adds substantial behavior beyond that: up to 25 results per call, best-match ordering with a query and newest-first otherwise, total match count, and lifetime/link fields on every job. There is no contradiction with annotations.

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?

The definition is front-loaded with what the tool returns, then organized into a useful "How to search well" list. It is longer than strictly necessary for a tool description, but most sentences contribute concrete operational guidance rather than filler.

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?

Given the 10-parameter search surface and the existing output schema, the description is complete enough for correct invocation: it covers the main filter constraint, search strategy, ordering, result limit, and important returned fields. The annotations and output schema carry the rest of the safety and return-shape burden.

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 description coverage is 60%, so the description carries meaningful additional semantics: query words must all match, short title/skill terms work best, and at least one of query/company/city/country should be supplied. It also clarifies country codes and common listing geography, though it leaves some parameters such as offset and salary_min mostly to the schema.

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 description gives a specific verb and resource ("Search open jobs on Ocean of Jobs") and immediately explains scope, result ordering, and key return fields. It also distinguishes itself from the detail sibling by instructing the agent to use get_job for 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 Guidelines5/5

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

It explicitly states that at least one of query, company, city, or country should be provided, and gives clear search tactics: use short core terms, search once, broaden once if needed, deduplicate by id/apply_url, and open only the strongest candidates with get_job. This is unusually complete when-to-use and how-to-use guidance.

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

All Ocean of 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.