Skip to main content
Glama

jobstack-mcp

by io.github.IsaiahDupree

Search jobs (unified feed)

search_jobs
Read-onlyIdempotent

Search job postings across every configured source and merge the results into one flat Job shape. Fans out in parallel to USAJOBS, Adzuna, Jooble, The Muse, Reed, and the ats engine (Greenhouse/Lever/Ashby/Workable/SmartRecruiters), then merges + sorts by postedDate (newest first) and paginates the combined set. Each Job has id, source, title, company, location, remote, url, description, postedDate, salaryMin, salaryMax, salaryCurrency, department, and employmentType. The response envelope carries meta, the echoed query, sources_requested, an optional sources_errored map, total, count, limit, offset, and results. Use sources= to restrict to specific engines.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results in the merged page, clamped 1-100. Default 20.
offsetNoZero-based offset into the merged result set for pagination. Default 0.
remoteNoFilter to remote roles when true. Only sources that expose an explicit remote signal apply it; others ignore it.
sourcesNoComma-separated engine keys to restrict the fan-out to. Any of: usajobs, adzuna, jooble, themuse, reed, ats. Omit for all six.
keywordsNoFree-text search terms (job title, skill, company, etc.). Optional — omit to browse the latest postings.
locationNoFree-text location filter (e.g. "Washington, DC" or "London"). Applied upstream where the source supports it.

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/destructive annotations, the description reveals significant behavior: parallel fan-out to six sources, merging/sorting by postedDate, pagination of the combined set, and an optional 'sources_errored' map for partial failures. This is valuable context that annotations alone do not provide.

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?

The description is one dense but well-organized paragraph. The first sentence states the core purpose, and each subsequent sentence earns its place by covering sources, merge/sort/pagination, the Job shape, the response envelope, and usage tip. No filler or redundancy.

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?

With no output schema, the description fully specifies the Job fields and the response envelope (meta, sources_errored, total, count, limit, offset, results), along with error behavior. This gives an agent everything needed to interpret the result. Combined with the strong annotations, this is complete for a complex search tool.

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?

The input schema already covers all parameters with detailed descriptions. The description adds meaning by explaining that limit/offset apply to the merged set after sorting by postedDate, and clarifies the 'sources' parameter's role in restricting fan-out. This context helps interpret pagination and filtering semantics 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?

The description opens with a specific verb+resource: 'Search job postings across every configured source and merge the results into one flat Job shape.' It clearly distinguishes from the sibling tool get_job, which presumably retrieves a single job, by emphasizing the unified multi-source feed.

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?

The description states when to use the tool (search across all sources) and gives basic guidance ('Use sources= to restrict to specific engines'). However, it does not explicitly say when not to use it or direct users to get_job for single-job lookups, so it lacks an explicit alternative mention.

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

All jobstack-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

The two tools have clearly distinct purposes: search_jobs queries across sources and returns a list, while get_job fetches a single job by its source and native ID. There is no overlap in functionality or confusion about when to use each.

Naming Consistency5/5

Both tool names follow the same verb_noun pattern: 'search_jobs' and 'get_job'. The verbs are descriptive and the naming convention is consistently lowercase with underscores, making the API predictable.

Tool Count3/5

With only two tools, the surface feels thin for a job search platform. While the pair covers search and retrieval, a typical server might include additional utilities like listing sources or fetching by internal ID. The count is borderline but not extreme.

Completeness4/5

The core workflow of searching for jobs and fetching details is fully covered. Minor gaps exist, such as no explicit endpoint to list available sources and the limitation that some upstream sources don't support single-job lookup, but these can be worked around or are inherent to external APIs.

Resources