Skip to main content
Glama

SteadyScrape Jobs Data

Search jobs across company career sites

search_jobs
Read-only

Search job titles across our index of company career boards (Greenhouse, Lever, Ashby, Workday and more), newest first: title, company, location, remote flag, salary when published, posting date and job URL. Filter by country, location text, remote, company and posting age. Billed per job returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "keywords": "<keywords>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoJobs to return in total (default 20, max 50). Billed per job returned.
keywordsYes1-5 job title terms, e.g. "data engineer". A job matches if its title has all words of any term.
companiesNoOptional company names or board slugs.
countriesNoOptional ISO country codes or names, e.g. US, GB, Germany.
locationsNoOptional location text, e.g. Berlin, New York, California.
remote_onlyNoOnly remote jobs (default false).
posted_within_daysNoOnly jobs posted in the last N days.
include_descriptionsNoInclude the first 1,500 characters of each description as plain text (default false). Not billed extra.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint true), so the bar is lower. The description still adds real value beyond them: results are ordered newest first, salary is included only when published, and crucially 'Billed per job returned' surfaces a cost consequence the annotations never mention. It does not explain why idempotentHint is false or whether repeated calls return changing results, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with a colon-delimited field list; the purpose and data sources are front-loaded before the filter and billing details. Nothing is redundant with the title, and the cost note is placed last where it is still visible.

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?

With 8 parameters, full schema coverage and no output schema, the description correctly compensates by enumerating the returned fields (title, company, location, remote, salary, posting date, URL). Cost and ordering are also disclosed. It lacks only guidance on result volatility or pagination behavior beyond the limit parameter.

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 description coverage is 100% and every parameter, including limits, defaults and the keyword matching rule, is fully documented in the schema. The description only restates the filter list and adds the ordering fact, which is about output rather than parameter meaning. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

The description opens with a specific verb and resource ('Search job titles across our index of company career boards') and names the ATS sources (Greenhouse, Lever, Ashby, Workday). It also enumerates the returned fields, so an agent knows exactly what a result contains. It stops short of distinguishing itself from siblings like company_jobs or remote_jobs, which is the only thing keeping it from a 5.

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?

It states what can be filtered (country, location text, remote, company, posting age) and that results come newest first, which implies the use case of broad title search. But there is no explicit when-to-use clause and no contrast with company_jobs or remote_jobs, so the agent must infer which sibling to pick.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources