Skip to main content
Glama
foundrole

FoundRole MCP

Official
by foundrole

jobs_search

Find job listings that match your criteria by searching live postings, with filters for location, company, remote work, salary, and H1B sponsorship.

Instructions

Searches a database for real-time job listings matching the user's criteria.

The query is the full job title or role: "Ruby Developer" or "Ruby on Rails Engineer" rather than a bare keyword like "Ruby", which is too broad and matches unrelated fields. Results may be filtered by location, company, and how recently a job was posted.

Each result carries an id; jobs_details takes that id and returns the job's full description, requirements, and benefits. The response also carries a nextCursor for the next page of results; a follow-up page is fetched by passing only that cursor, with no other search parameters.

Authenticated results include resume match data when a profile is available. Job details include FoundRole salary benchmarks, H-1B sponsorship signals, E-Verify status, and job-trust analysis; list-level employer signals follow the user's current entitlements.

Advanced constraints in the user's request — remote-only work, H1B sponsorship, a minimum salary, hiding risky postings, a minimum match score — are the search parameters remote, h1b_sponsors_only, salary_floor, hide_low_quality, and min_match. The search enforces only constraints passed as parameters; a constraint left out of the call is not applied to the result set. FoundRole Pro accounts receive the screened list; other accounts receive the full list and the response reports that the advanced filters were not applied.

Each response includes a system_instruction describing how to present the results for the current client.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoThe full job title or skill (e.g., "Ruby Developer", NOT just "Ruby")
cursorNoPagination cursor. Treat as an opaque string. COPY EXACTLY.
remoteNoAdvanced filter: only remote-eligible jobs (respects the location/region scope).
companyNoThe official company name
locationNoGeographic location (e.g., 'Boston, MA')
min_matchNoAdvanced filter: minimum personal FoundRole match score (0-100); needs a resume on the account.
salary_floorNoAdvanced filter: minimum annualized salary in USD; a posting qualifies when the midpoint of its pay band reaches the floor. Jobs without salary data are dropped.
posted_days_agoNoNumber of days ago to search for jobs (1-365)
hide_low_qualityNoAdvanced filter: hides postings with a risky ghost grade (D/F); ungraded postings stay.
h1b_sponsors_onlyNoAdvanced filter: only companies known to sponsor H1B visas.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobsNo
feedKindNo
feedStatusNo
jobSearchIdNo
statusOrderNo
revalidatingNo
trackerWebUrlNo
profileSetupUrlNo
profileSetupStateNo
lowRelevanceNoticeNo
proFilterUpsellUrlNo
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no meaningful annotation hints (readOnlyHint false does not indicate side effects), the description carries the burden and does well: it reveals that only passed parameters are enforced, that Pro accounts receive a screened list while others get the full list, and that responses include a system_instruction. This goes beyond the schema and annotations, though it omits potential error scenarios or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured but verbose, with multiple paragraphs covering job details, account tiers, and response instructions that may extend beyond the search action itself. While each sentence adds some context, the length could be trimmed without losing core meaning, making it less concise that ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, output schema, heterogeneous behaviors), the description is remarkably complete: it covers pagination via `nextCursor`, authentication-based resume data, Pro vs. non-Pro filtering behavior, and the presence of `system_instruction` in responses. The existing output schema handles return structure, so no further detail is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, giving a baseline of 3. The description adds value by explaining the query parameter format ('full job title or role'), explicitly listing the advanced filters and how they map to parameters, and clarifying that omitted constraints are not applied. This enhances semantics beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear, specific statement: 'Searches a database for real-time job listings matching the user's criteria.' It distinguishes itself from sibling tools by explicitly mentioning jobs_details for fetching full job descriptions using the `id` from search results, and it implies a search-specific role relative to recommendation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on how to use the search (e.g., use full job titles, not bare keywords) and directs to jobs_details for full descriptions. However, it does not explicitly state when not to use this tool or mention alternatives such as jobs_recommendations, though the query guidance and mention of jobs_details offer partial differentiation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/foundrole/jobs-mcp-proxy'

If you have feedback or need assistance with the MCP directory API, please join our Discord server