Skip to main content
Glama

PickedJobs

Search jobs

search_jobs
Read-onlyIdempotent

Search open jobs on PickedJobs. Returns up to 30 jobs per page, newest and most relevant first, with salary, seniority, remote policy, regions and stack. Each job uses one job from the account’s daily allowance the first time the account receives it in a UTC day; jobs already received that day use none. Values within a field match any selection; different fields are combined. Results include each job's slug; full descriptions are available by slug.

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": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoKeywords matched against job title, company and stack, e.g. "platform engineer".
pageNoPage of 30 results, from 1.
roleNoOne or more engineering specialties. Implies category engineering.
stackNoOne or more technologies. Matches jobs mentioning any selected technology.
regionNoOne or more regions the candidate can work from.
remoteNoOne or more arrangements: remote, remote_region, hybrid or onsite.
companyNoCompany slug from a previous result's companySlug.
categoryNoKind of role.
salaryMinNoMinimum pay. Only matches jobs that publish salary. Defaults to USD per year.
seniorityNo
employmentNoOne or more employment types. eor: hired through an employer of record.
postedWithinNoOnly jobs posted in the last N days.
salaryPeriodNo
salaryCurrencyNoISO currency code for salaryMin, e.g. USD, EUR, GBP.
visaSponsorshipNoOnly jobs whose posting says the employer sponsors visas. Most postings don't say either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish the safe read-only, idempotent profile, so the description's job is behavioral context — and it delivers the notable quota rule (a job consumes one of the account's daily allowance the first time it is received in a UTC day, zero afterwards) plus the 30-per-page ordering. These are facts available nowhere in the schema and materially affect how an agent should call the tool.

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?

Four sentences, each carrying distinct information: result shape, page size and ordering, quota accounting, and retrieval-by-slug. No filler and the result contract is front-loaded.

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 15-parameter, zero-required search tool with no output schema, the description covers result shape, ordering, page size, matching semantics and quota cost — everything needed to call it safely. It omits default values (page 1, USD per year) and the page-334 ceiling, which the schema does carry.

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?

With 87% schema coverage the baseline is 3, and the description earns an extra point by explaining the combination logic: values within a field are OR'd while different fields are AND'd. That query semantics is not stated in the schema and directly shapes how an agent builds multi-value calls.

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 — 'Search open jobs on PickedJobs' — and enumerates what comes back (salary, seniority, remote policy, regions, stack). It does not distinguish itself from the close sibling get_new_jobs, leaving an agent to guess which search path to take.

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?

Usage is only implied: the closing line about slugs hints that get_job fetches full descriptions, which is a useful routing cue. There is no explicit statement of when to prefer this over get_new_jobs or the saved-search tools, and no prerequisites are given.

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