Skip to main content
Glama
Sign In
mcp-job-search

mcp-job-search

by michalper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_jobs

Search job-board APIs by keywords, location, and remote preference to find normalized postings. Returns source errors when a provider is unavailable or unconfigured.

Instructions

Searches real job-board APIs (Arbeitnow — free, always on; Adzuna and JSearch — only if their API keys are configured via environment variables). Returns normalized jobs plus a list of source errors (e.g. a source skipped because its key isn't set) — never raises on a single source's failure. Results are cached by query for SEARCH_CACHE_TTL_SECONDS (default 6h) to protect JSearch's free quota; pass use_cache=False to force a fresh query. This does NOT scrape or search sites without a public API (e.g. NoFluffJobs, JustJoin.it, Pracuj.pl) — use fetch_job_posting for a specific URL on those instead.

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
sourcesNoLimit to these source names, e.g. ['arbeitnow']. Default: all.
keywordsYesKeywords to match, e.g. 'PHP Magento backend'.
locationNoFree-text location filter, e.g. 'Poland'.
use_cacheNoReuse a cached result. False forces a fresh query.
remote_onlyNoOnly return remote-flagged postings.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses conditional source availability (Adzuna/JSearch only with env-var keys), graceful degradation (never raises on a single source failure, returns source errors), and a caching policy with TTL default 6h tied to protecting JSearch's free quota.

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?

Three front-loaded sentences covering capability, failure/caching behavior, and exclusions; each earns its place. The middle sentence is dense with several clauses but remains scannable.

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

Completeness5/5

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

An output schema exists, so return-value shape needn't be spelled out, yet the description still summarizes the payload (normalized jobs plus source errors). For a multi-source, cached search tool this covers everything an agent needs to call it correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds the rationale behind use_cache (quota protection, TTL default) that the schema only states mechanically. It does not add meaning for location/remote_only/sources beyond 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?

Opens with a specific verb+resource ('Searches real job-board APIs') and immediately names the concrete backends it hits (Arbeitnow, Adzuna, JSearch). It explicitly distinguishes itself from fetch_job_posting by declaring what it does NOT do (scrape sites without a public API).

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 explicit routing rules in both directions: use this for keyword search across API-backed boards, use fetch_job_posting for a specific URL on sites like NoFluffJobs/JustJoin.it/Pracuj.pl. It also states the use_cache=False escape hatch for forcing a fresh query.

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

Deploy Server

Other Tools