Skip to main content
Glama
job-board-mcp

job-board-mcp

by adeolaoj

search_jobs

Search open jobs across configured company job boards, newest first, and filter by career lane, company, location, remote status, keywords, or posting age to find relevant roles.

Instructions

Search open jobs across the configured companies' job boards, newest first.

All filters are optional and combine (a job must pass every filter given).
Returns `jobs`, `total_matches` (before `limit`), `errors` (companies that couldn't be
searched, or unknown company names), and `warnings` (individual postings skipped
because of bad data). To read a job's full description, pass its `company` and
`job_id` to get_job.

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
laneNoCareer lane, matched against job titles: 'deployment' (forward deployed, solutions, implementation, and customer engineering roles), 'pm' (product and technical program management), 'new_grad' (new grad, early career, and graduate programs). Senior, staff, principal, director, lead, and intern titles are never in any lane. Omit to search every title.
limitNoMax jobs to return, newest first. total_matches still counts every match.
remoteNotrue: only jobs the board marks as remote. false: only jobs it marks as onsite or hybrid. Uses the board's structured workplace field, not the location text. Many jobs don't say either way and are left out by both true and false, so omit this unless remote matters.
keywordsNoWords to find in job titles; a job matches if ANY keyword appears as whole words, in order ("product manager" matches "Senior Product Manager" but not "Product Marketing Manager"). Ignores lane exclusions, so senior roles can match.
companiesNoCompany names to search, from list_companies (case doesn't matter). Omit to search all.
locationsNoPlaces to find in the job's location text; a job matches if ANY entry appears. Boards write places differently, so pass synonyms together, e.g. ["new york", "nyc"] or ["san francisco", "sf", "bay area"]. Use `remote` for remote work, not "remote" here.
posted_within_daysNoOnly jobs first posted within this many days, e.g. 7 for the last week.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does real work: it discloses ordering (newest first), AND-combination of filters, the exact response keys, that total_matches is counted before limit, and the distinct meaning of errors (unsearchable/unknown companies) versus warnings (skipped bad postings). It does not mention permissions, configuration state, or pagination beyond limit, so the behavioral picture is strong but not exhaustive.

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?

Front-loaded with the core action and scope in the first sentence, then filter semantics, then return shape, then the handoff to get_job. Every sentence carries information, and the return-value enumeration is justified because there is no output schema.

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?

Seven optional parameters at 100% schema coverage with no annotations and no output schema — the description compensates by explaining filter combination and enumerating the return keys, plus pointing to get_job for full descriptions. An agent has everything needed to invoke it correctly and interpret the result.

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 100%, so the baseline would be 3; the description earns above that by adding cross-parameter semantics not encoded in the schema — that all filters are ANDed together and that any given job must pass every filter supplied. Individual filter behavior (lane matching, whole-word keyword logic, remote's exclusion of unlabeled jobs) is already covered by the schema's own descriptions, so this is incremental rather than comprehensive.

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 open jobs"), the scope ("configured companies' job boards"), and the ordering ("newest first"). It also routes the agent to the sibling that handles the complementary need ("To read a job's full description ... get_job"), so it is distinguishable from both siblings without opening a schema.

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?

Makes clear the tool is the listing/search entry point and explicitly hands off detail retrieval to get_job, plus notes all filters are optional and combinable. It does not state any explicit when-not-to-use condition (e.g., use list_companies first to discover valid company names), so it stops short of full routing guidance.

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