Remote Jobs MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_jobsA | Legacy-compatible public jobs feed. Keeps the original full job objects and JSON array in content.text. Use search_jobs for compact results and more filters. Geo means candidate eligibility: country, parent region, or globally available jobs may match. No authentication. |
| get_taxonomiesA | Legacy-compatible location or industry lookup. Returns the original JSON in content.text. Call when a filter slug is uncertain; obvious values can go directly to search_jobs. |
| search_jobsA | Search public remote jobs with compact results, without full descriptions. Geo uses candidate eligibility, including eligible parent regions and global jobs. Call directly when filters are clear; use resolve_taxonomy for uncertain slugs. Cursor is opaque: pass nextCursor unchanged with identical filters. jobCount counts this page only. |
| get_jobA | Fetch the full public description and details of one visible job by ID. Use after search_jobs when the complete vacancy is needed. |
| get_similar_jobsA | Recommend a small set of public jobs related to one job. Deterministic score weights shared industry 3, type 2, level 2, location 1, title word 2. Scores are relevance weights, not probabilities. |
| search_companiesA | Find specific public companies by name, company industry, or headquarters text. A search criterion is required. Returns at most 10 companies, with no cursor or overall count; this is not a company directory export. |
| get_companyA | Get public details of one company by stable ID or slug, including its description, website, categories and headquarters when available. |
| get_company_jobsA | Get compact public jobs for one published company. Cursor is opaque; pass it unchanged with the same companyId. |
| get_roleA | Get a public Jobicy career role guide by its /careers/ slug, including existing overview, skills, responsibilities and levels. |
| get_related_rolesA | Get a small deterministic set of roles sharing the same Jobicy career category as the requested role. |
| resolve_taxonomyA | Resolve an ordinary location or industry name to a real Jobicy slug. Use when unsure of a slug; low-confidence matches return candidates without selecting one. |
| list_taxonomiesA | List public filter slugs and labels for locations, industries, job types or job levels. No job or company counts are included. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target distinct resources and actions, and descriptions explicitly differentiate the legacy tools (get_jobs, get_taxonomies) from their modern counterparts (search_jobs, list_taxonomies). The taxonomy trio (get_taxonomies, list_taxonomies, resolve_taxonomy) and the two job-search tools still require reading the descriptions to distinguish, but the guidance is clear.
All twelve tools follow a consistent verb_noun (or verb_noun_noun) snake_case pattern: get_job, search_jobs, list_taxonomies, resolve_taxonomy, get_company_jobs, etc. No mixed conventions or vague verbs.
Twelve tools is well within the ideal 3-15 range and each maps to a distinct facet of the domain (jobs, companies, roles, taxonomies). No tool feels redundant enough to be padding, aside from the intentional legacy-compatible pair.
The read-only surface covers jobs (search, detail, similar), companies (search, detail, jobs), roles (guide, related), and taxonomy resolution/lookup, giving solid lifecycle coverage for a public jobs API. Minor gap: no bulk/aggregate or saved-search style operations, but these are reasonable omissions for a read-only public feed.