Ocean of Jobs

Get a job

get_job

Read-onlyIdempotent

One job on Ocean of Jobs by its id (from search_jobs or get_company): the description as plain text, its lifetime, whether its data is verified against the employer's ATS, and both links, the Ocean of Jobs page first.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	The job's id, e.g. 67ff4ef965d91ef7.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`url`	Yes	The listing's page on Ocean of Jobs. Show this first.
`title`	Yes
`company`	Yes	The employer's name, or its domain when the ATS gives no name.
`category`	Yes
`lifetime`	Yes	first_seen is when Ocean of Jobs first found the listing on the employer's own applicant tracking system. last_seen is the last time a read of that board returned the listing with any change; a board that answers 'unchanged' was still checked, so the listing may have been confirmed more recently than last_seen says. closed_at is when a successful read of the board no longer included it; null means it was still listed at the last successful read. reappeared_at is when this same listing (the same ATS id) was last seen again after being missing from our reads of the board for at least two days; null means no such absence was seen (recorded since 2026-10-19). It says what was observed, not that the employer reposted it: our own failed reads can look the same, so do not call a listing reposted on this or on an old first_seen. A new posting for the same role is a new listing. posted_at is the employer's own date where the ATS gives one, and can be missing.
`location`	Yes
`apply_url`	Yes	The employer's own application page.
`seniority`	Yes
`workplace`	Yes
`confidence`	Yes	verified: read from the employer's ATS API. best_effort: from the careers page markup.
`department`	Yes
`description`	Yes	Plain text; '## ' starts a heading and '- ' a bullet. Null when the ATS gave none.
`company_domain`	Yes
`description_truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that the result includes verification against the employer's ATS and link ordering, but since an output schema exists this return-content detail is largely redundant.

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?

A single dense sentence that front-loads the resource and scope; the enumeration of returned fields is a bit run-on but every clause carries information.

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 single-parameter read tool with an output schema and full annotation coverage, the definition is nearly self-sufficient; the only minor gap is that return-value details duplicate the output schema.

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 id format is already documented. The description goes beyond the schema by stating the provenance of the id (from search_jobs or get_company), which is genuinely useful for constructing the call.

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 ('One job on Ocean of Jobs by its id') and names the siblings that supply the id (search_jobs, get_company), so an agent can distinguish it from those tools without inspecting schemas.

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?

It clearly routes the agent by naming where the required id comes from (search_jobs or get_company), which implies this tool is the follow-up step. It lacks an explicit 'do not use this for searching' exclusion, but the context is unambiguous.

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.