getonbrd-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GETONBRD_API_TOKEN | No | Optional API token from getonbrd.com/api used to enable the `get_job` tool. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_jobsA | Full-text search over Get on Board job listings (LATAM tech jobs). Returns compact job objects with salary band, remote modality, countries and application count. Search results include the job description, so no extra call is needed to triage. |
| jobs_by_categoryA | List open jobs in one category. Use list_categories for valid ids (e.g. "programming", "machine-learning-ai", "sysadmin-devops-qa"). |
| jobs_by_companyA | List open jobs published by one company. The company id is its slug on getonbrd.com, e.g. "2brains" for getonbrd.com/companies/2brains. |
| list_categoriesA | List all job categories with their ids (paginated; there are ~6 pages by default page size). |
| get_jobA | Fetch one job by id (the slug in its URL). Requires GETONBRD_API_TOKEN — without it the API returns 401; prefer search_jobs, whose results already include descriptions. |
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 5 tools
Each tool targets a clear dimension: full-text search, category browsing, company browsing, category metadata, and single-job lookup. search_jobs and get_job overlap somewhat because search results already include descriptions and get_job requires a token, but the distinct id-based lookup purpose remains identifiable.
Names mix verb-led patterns like search_jobs, list_categories, and get_job with noun-preposition patterns like jobs_by_category and jobs_by_company. The naming is readable and consistently lowercase snake_case, but the two conventions are not fully uniform.
Five tools is well-scoped for a job-board MCP server. Each tool maps to a distinct operation needed for job discovery and retrieval, with no obvious bloat or redundancy.
Core job discovery is covered: full-text search, category browsing, company browsing, category listing, and individual job details. A minor gap is the lack of a company listing endpoint to discover company slugs, but agents can work around it with jobs_by_company when slugs are known.