MCP server for searching remote technology job offers and accessing job details with optional application link access
Three tools with complete schemas and descriptions. Naming follows verb_noun pattern (search_jobs, get_job, open_application_link). Descriptions are adequate (50-100 chars) but lack actionable context for LLM selection. Parameters have types and descriptions, but missing enums for categorical fields (category, employmentType, jobType, remoteLocation). Error handling is present but generic. Output schemas are not documented. search_jobs accepts pagination (page, limit) but no total count or next_cursor guidance in description.
Get the public details and description of one remote job offer.
Get the original application link. The API key owner must have an active access subscription.
Search remote technology job offers. Returns public job details but never the original application URL.
Missing enum constraints for categorical parameters. 'category', 'employmentType', 'jobType', and 'remoteLocation' accept free-form strings, inviting hallucinated values. LLMs cannot infer valid options without enums.
Output schemas not documented. Callers cannot predict response structure (fields, types, nesting). LLMs must guess what fields to extract for downstream tool calls.
search_jobs pagination lacks guidance. Description does not explain total count, next_cursor, or result limits. Agents cannot determine if more results exist or how to fetch them.
Descriptions lack context for LLM selection. 'Get the public details and description of one remote job offer' does not explain when to call get_job vs search_jobs or what data is returned.
Inferred effective spec: 2025-06-18+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2025-06-18+ | v2 |
open_application_link description omits prerequisite. Does not state that an active subscription is required until the error is returned. LLMs should know this upfront to avoid wasted calls.