Skip to main content
Glama

search_jobs

Find open jobs by query across saved or specified company career pages and free job boards, with filters for remote work, location, and posting date; results are ranked by relevance.

Instructions

Search open jobs, best matches first.

Searches your saved companies' hiring systems (or the companies given: names or careers-page URLs) plus free job sources (Hacker News "Who is hiring?", Arbeitnow, Himalayas) when sources="all". remote=True: remote only; False: no remote; null: either. Jobs from company hiring systems are "open"; jobs from free sources are "unverified" (use check_job). Max 100 results.

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": {
      "query": "<query>"
    },
    "name": "search_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
remoteNo
sourcesNoall
locationNo
companiesNo
posted_within_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full load; it does disclose result ordering, a 100-result cap, and a trust distinction between verified and unverified postings, which is real behavioral value. It omits prerequisites (does it require saved companies to exist?), whether the call is read-only/side-effect free, and how results are structured or paginated.

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 action and ranking note, then dense supporting clauses with no filler. The parenthetical asides and mixed sentence fragments make it slightly denser than ideal, but every line conveys information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with no annotations and no output schema, the description covers the important behavioral axes (sources, remote, verification status, result cap) but leaves two parameters unexplained and gives no sense of what a returned job record contains. Adequate but with clear gaps an agent would have to discover by calling it.

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 0%, so the description must compensate; it explains the tri-state remote semantics, the sources enum values, and that companies accepts names or careers-page URLs. However, location and posted_within_days are never mentioned, and the relationship between the 100-result cap and the limit parameter is only implied.

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 opening sentence names a specific verb and resource ('Search open jobs') and adds ranking behavior ('best matches first'). The body clarifies what corpus is searched (saved companies' hiring systems plus free sources), which makes the tool distinguishable in substance, though it never explicitly contrasts itself with siblings like company_jobs or search.

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

Usage Guidelines4/5

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

It gives conditional guidance: free sources are only queried when sources="all", and company-system jobs are 'open' while free-source jobs are 'unverified', directing the agent to check_job in that case. It doesn't say when to prefer this over sibling search tools, but the in-tool routing guidance is clear.

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