jobs.listings.search
Search global job listings via CareerJet — title, company, salary, location, contract type across 90+ countries
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/jobs.listings.search.md
What jobs.listings.search does on Apibase
AI agents call jobs.listings.search to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | — | Page number (1-10). Default: 1. |
sort | string | — | Sort order for results. Default: "relevance". |
keywords | string | Yes | Job search keywords (e.g. "software engineer", "marketing manager remote"). |
location | string | — | Location filter (e.g. "New York", "London", "Berlin"). Omit for worldwide. |
page_size | integer | — | Results per page (1-100). Default: 20. |
work_hours | string | — | Filter by work hours: full_time or part_time |
locale_code | string | — | Locale code for results (e.g. "en_US", "en_GB", "de_DE"). Default: "en_US". |
contract_type | string | — | Filter by contract type. |
Parameters from the server's own tool schema.
Why jobs.listings.search is rated Low
Tool retrieves job listing data with no side effects or data modification capability.
From the tool's definition Search global job listings via CareerJet — title, company, salary, location, contract type
Attacks that exploit this kind of access
The rule that runs jobs.listings.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jobs.listings.search, this is the rule to start with:
jobs.listings.search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every jobs.listings.search call is checked against it from then on.
Questions about jobs.listings.search
Search global job listings via CareerJet — title, company, salary, location, contract type across 90+ countries. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
jobs.listings.search accepts 8 parameters: page, sort, keywords, location, page_size, work_hours, locale_code, contract_type. Required: keywords. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for jobs.listings.search: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Apibase. Nothing to install.
jobs.listings.search is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the jobs.listings.search rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for jobs.listings.search. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
jobs.listings.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue