Skip to main content
Glama
Sign In

highbrow_fame data APIs (pay per call)

by io.github.projectworks007
OverviewDiscussionsAdmin

Live job ads from one job board

jobs_search
Read-only

Live job ads from one job board per call: Seek, Dice, Google Jobs, Naukri, JobStreet/JobsDB, jobs.ch, Job Bank Canada, Foundit, NaukriGulf, PNet, MyCareersFuture, elempleo or a remote-jobs aggregator. Returns title, company, location, work type, salary where shown, posting date and link. Suited to job search and hiring-market questions. $0.02 per call, up to 25 ads.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jobs_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoJob board key from /jobs/sites, e.g. google-jobs, seek, naukri, jobstreet-jobsdb, dice, jobs-ch. google-jobs: Google job search (jobs from every board and career site Google indexes), up to 10 jobs per request.
inputNoAdvanced: a JSON object with the site's own filters; GET /sites lists them per site.
limitNoMaximum results (default 20).
queryNoKeywords, e.g. "data analyst".
countryNoCountry code for sites that have editions: google-jobs (any, e.g. us, gb, de, in), seek (au, nz), jobstreet-jobsdb (my, sg, ph, id, hk, th).
detailsNoInclude the full ad text where the site offers it.
locationNoCity, region or postcode as the site understands it, e.g. "Berlin".
searchUrlNoInstead of query/location: a full search-results link from the site, with its filters.
postedWithinDaysNoOnly ads posted in the last N days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, openWorld), and the description adds genuinely useful behavior beyond them: cost of $0.02 per call, a result ceiling of up to 25 ads, and the per-call single-board constraint. It does not mention pagination behavior or whether failures on an invalid board key error out, but the cost and cap disclosures are substantive.

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 statement, then the return fields, then the use case and cost. The long board enumeration is the bulkiest element but it is the sort of concrete detail an agent needs; otherwise there is no filler.

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 nine-parameter, all-optional, open-world search tool with no output schema, the description covers inputs, returned fields, cost, and result cap, which is most of what an agent needs to call it correctly. The remaining gap is guidance on selecting a board key, which the schema partially covers via examples.

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

Parameters3/5

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

Schema coverage is 100%, so all nine parameters are already documented in the schema with examples. The description reinforces the single-value nature of 'site' by framing it as one board per call, but adds no syntax or format detail beyond what the schema supplies; baseline 3 applies.

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 ('Live job ads from one job board per call') and enumerates the boards and the fields returned (title, company, location, work type, salary, posting date, link). It is unmistakably a job-posting search tool, though it never names or contrasts a sibling (e.g. classifieds_search) that an agent might confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The line 'Suited to job search and hiring-market questions' gives positive usage context, and 'one job board per call' hints at how to invoke it repetitively. There is no when-not guidance, no statement about which board to choose for a given geography, and no explicit alternative tool routing.

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

All highbrow_fame data APIs (pay per call) toolsInspect
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