Skip to main content
Glama

getwork.dev

Search developer jobs

search_jobs
Read-onlyIdempotent

Search active developer jobs with structured filters (stack, seniority, role family, region, country, remote, salary floor, company, exclusions). Use this when you know the filters; for a request in plain words use search, which reads the sentence into these same filters. Returns up to limit compact JobSpecs (no description) sorted by relevance or recency, the total and next_offset for paging. Then call get_job for the full posting.

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
limitNo
queryNoFree text, e.g. 'distributed systems' or 'payments'. Every word must match (a word also matches its synonyms).
stackNoTechnology tags that must all be in the role's primary stack (any one of them with stack_any), lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match.
offsetNo
remoteNo
companyNoCompany slug from list_companies.
excludeNoLeave out jobs matching any of these: a stack tag (not in the primary stack or title), a role family, or a topic like 'crypto' or 'gambling' (not mentioned anywhere, synonyms included).
regionsNoAny of these regions. Worldwide-remote jobs are always included.
collapseNoGroup the same role posted for several locations into one result; same_role_other_locations tells how many more exist.
currencyNoISO currency code (EUR, USD, GBP). Restricts to jobs that publish pay in this currency.
countriesNoISO 3166-1 alpha-2 codes, e.g. NL, DE, GB. Common country names (Netherlands, UK) are read too.
seniorityNo
stack_anyNoAny one of the stack tags will do instead of all of them: 'Go or Rust'.
min_salaryNoMinimum yearly salary (upper end of the published range must reach it), in `currency`. Without a currency it is compared against USD, EUR, GBP, CHF, CAD, AUD, NZD and SGD ranges as written.
role_familyNo
salary_requiredNoOnly jobs that publish a salary range.
posted_within_daysNo

Output Schema

NameRequiredDescriptionDefault
jobsYes
totalYes
offsetNo
next_offsetNo
security_noticeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / countries / description
      Previous value: -"ISO 3166-1 alpha-2 codes, e.g. NL, DE, GB."New value: +"ISO 3166-1 alpha-2 codes, e.g. NL, DE, GB. Common country names (Netherlands, UK) are read too."
    • changedInput schema / properties / min_salary / description
      Previous value: -"Minimum yearly salary (upper end of the published range must reach it). Combine with currency."New value: +"Minimum yearly salary (upper end of the published range must reach it), in `currency`. Without a currency it is compared against USD, EUR, GBP, CHF, CAD, AUD, NZD and SGD ranges as written."
  2. Changed2 schema fields changed
    • changedInput schema / properties / stack / description
      Previous value: -"Technology tags that must all be in the role's primary stack, lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match."New value: +"Technology tags that must all be in the role's primary stack (any one of them with stack_any), lowercase: rust, go, typescript, python, react, postgres, kubernetes, ... Passing mentions (stack_mentioned) do not match."
    • addedInput schema / properties / stack_any
      Added value: +{
      +  "default": false,
      +  "description": "Any one of the stack tags will do instead of all of them: 'Go or Rust'.",
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / offset / maximum
      Added value: +200
  4. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already carry readOnly/idempotent/closed-world, and the description adds genuinely new behavior: results are 'active' jobs only, compact JobSpecs with no description field, capped by `limit`, sorted by relevance or recency, and paged via total/next_offset. It does not discuss rate limits or what happens if a filter combination yields zero results, but the important caveat (missing descriptions, hence the get_job pointer) is disclosed.

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?

Three sentences, front-loaded with purpose, then routing, then return shape and next step. No restatement of the title and 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 17-parameter search tool with an output schema, the description covers the essentials an agent needs: what is returned, that descriptions are omitted, pagination fields, and the natural next call. Details like default collapse grouping and offset ceiling are left to the schema, which documents them, so nothing critical is missing.

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 65%, so the description must add something; it groups the 17 params into recognizable filter families and flags non-obvious ones like exclusions and the salary floor. It does not explain `query`, `collapse`, `stack_any`, `offset`, or `posted_within_days` semantics, leaving the remaining gap to the schema.

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 (search active developer jobs) plus the filter axis set, and explicitly distinguishes itself from two siblings: `search` for plain-language requests and `get_job` for full postings.

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

Usage Guidelines5/5

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

Gives an explicit routing rule ('use this when you know the filters; for a request in plain words use `search`') and a follow-up step ('Then call get_job for the full posting'). The decision between tools is fully determined without opening any schema.

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