Skip to main content
Glama
Unified Jobs MCP Server

Unified Jobs MCP Server

by rezearcher

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_unified_jobsA

Cross-source job search that returns ONE deduplicated, field-unioned feed across applicant-tracking systems (Greenhouse, Lever, Ashby, SmartRecruiters, Workday, Recruitee, Workable), the LinkedIn public guest search, and the Hacker News "Who is hiring?" thread. The SAME role posted on several sources is merged into one canonical record with a sources[] array and a union of the richest salary / longest description / earliest posted_at — so you get a clean list, not three overlapping ones to dedupe yourself. Provide companies[] to pull their ATS boards, and/or keywords(+location) to search LinkedIn; HN returns the whole current thread (optionally keyword-filtered). At least one of companies[] or keywords is required unless hn is in sources. Returns canonical records plus dedup stats (cross_source_merges).

search_hn_hiringA

Search the CURRENT month's Hacker News "Ask HN: Who is hiring?" thread for live job postings, normalized into the same unified schema as search_unified_jobs. The monthly thread id is auto-discovered (it rotates on the 1st of every month) and each free-text post header is parsed into structured fields. No company list needed — this is the whole thread, optionally keyword / remote filtered. source_platform is "hn".

list_sourcesA

List the job sources this server merges across, how to address ATS companies, and how the cross-source dedup/merge behaves (canonical key, field union, degrade-open). No network call.

get_premium_accessA

Describe the metered depth endpoints available beyond this free server: a normalized cross-ATS compensation layer and a per-company hiring-intent signal. These are served pay-per-call over x402 (USDC on Base, no account/API key — the caller's wallet pays the 402 inline). Returns the base URL, each endpoint's path + USD price + what it adds, and the exact payment parameters. No network call, no payment.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation3/5

search_unified_jobs and search_hn_hiring overlap substantially: the unified tool already covers the HN thread as a source, so the dedicated HN tool is largely a subset of the general one. The descriptions do explain the difference (HN-only, no company list, whole thread), which keeps it usable, but an agent must read carefully to avoid redundant calls. list_sources and get_premium_access are clearly distinct from the search tools and from each other.

Naming Consistency5/5

All four names follow a clean verb_noun snake_case pattern: search_unified_jobs, search_hn_hiring, list_sources, get_premium_access. Verbs (search/list/get) accurately signal the operation type, and there are no style deviations.

Tool Count4/5

Four tools is on the thin side but defensible for a focused read-only job aggregator: two search entry points plus two metadata helpers. Nothing feels gratuitous, though the surface is small enough that a single search endpoint with source filters could arguably replace two.

Completeness3/5

The surface covers discovery well (cross-source search, HN search, source documentation), but there is no way to fetch a single canonical job record by id, no pagination/cursor continuation tool, and no detail endpoint for a merged record. get_premium_access is an informational upsell rather than a functional capability, which leaves the surface feeling search-only with dead ends after results are returned.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues