Skip to main content
Glama
job-board-mcp

job-board-mcp

by adeolaoj

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
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_companiesA

List the companies this server searches and which applicant tracking system each uses.

Use these exact names in search_jobs's `companies` filter and in get_job.
search_jobsA

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.
get_jobA

Get one job's full description as plain text, plus its title, location, URL, and posted date.

Pass `company` and `job_id` exactly as they appear in a search_jobs result.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool maps to a distinct step of a read-only workflow: list_companies enumerates sources, search_jobs queries them, get_job fetches one full description. Descriptions explicitly cross-reference each other (use these names in search_jobs; pass company/job_id to get_job), leaving no plausible misselection.

Naming Consistency5/5

All three follow a clean verb_noun snake_case pattern (list_companies, search_jobs, get_job). Verb choice is also semantically precise: list for enumeration, search for filtering, get for single-resource retrieval.

Tool Count5/5

Three tools is the minimum viable surface for discover-sources → search → inspect, and each earns its place with no redundancy. Nothing is padded or missing at the operation level.

Completeness4/5

The read-only lifecycle is fully covered end to end, including error/warning reporting in search results. Minor gaps: no explicit pagination/offset beyond limit, and no batch job-fetch, so an agent must loop on get_job for multiple postings.

Maintenance

ActivityMaintained
ResponsivenessOutdated data