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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_jobsA | Fetches a structured list of remote jobs from the Jobicy database. Safe GET request with zero side-effects. No authentication required. Returns a JSON object containing an array of job listings sorted by publication date, newest first. Each job object includes: id, url, jobTitle, companyName, companyLogo, jobIndustry, jobType, jobGeo, jobLevel, jobExcerpt, jobDescription, and pubDate. Always call 'get_taxonomies' first if you need to discover valid location or industry slugs to filter your search. Supports pagination via the 'count' parameter from 1 to 100. Rate limits: standard public web limits apply, avoid aggressive loop calls. |
| get_taxonomiesA | Retrieves available filter slugs for locations or industries to prevent formatting errors. Read-only metadata request with no side-effects. No authentication required. Returns a JSON object containing valid slugs. Use this tool before get_jobs when you need to verify if a specific region or category slug exists. |
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 2 tools
get_jobs retrieves job listings while get_taxonomies retrieves filter metadata, so the two tools have clearly distinct purposes. There is no overlap or ambiguity between them.
Both tools follow the same get_ noun pattern with snake_case naming. The names are predictable and clearly indicate that these are read-only retrieval operations.
Two tools is minimal, but it is not unreasonable for a narrow remote job lookup server. The count feels slightly thin rather than bloated or excessive.
The server covers the core read-only workflow: discovering valid taxonomy slugs and fetching paginated job listings with full descriptions. There could be additional conveniences like job detail lookup, but the primary use case is fully supported.