Skip to main content
Glama
foundrole

FoundRole Jobs - AI Job Search & Application Tracker

Official

Recommend jobs for my profile

jobs_recommendations
Idempotent

Returns personalized job recommendations based on your resume, skills, target roles, and location, ranked by fit and filterable by search criteria.

Instructions

Returns the authenticated user's personalized job recommendations built from their resume, skills, target roles, and preferred location. Results are ranked by fit, may include related roles, and carry the same salary, match, H-1B, and job-trust insight payload used by job search. The search filters and sort parameters apply to this personalized feed too. Advanced parameters return a matching preview and hidden count for free accounts; Pro accounts receive the complete filtered list. An explicit query for a different or unrecognized profession uses the same general job search as jobs_search, preserving the query and filters instead of substituting the profile's target roles.

A processing status means the personalized feed is still being prepared; a later call returns the completed feed. Page numbers fetch additional recommendations from the same feed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoRecommendation page number
sortNoResult order (score, posted_at, match, salary): score is relevance and the default, posted_at is newest first, salary is highest pay first, match is best personal fit first and needs a resume. Ordering by salary or match is an advanced option.
queryNoThe full job title or skill (e.g., "Ruby Developer", NOT just "Ruby")
radiusNoSearch radius in miles around a city location (default 40); not used for state, country or remote searches.
remoteNoAdvanced filter: only remote-eligible jobs, matched across the whole country of the requested location rather than its radius.
companyNoThe official company name
benefitsNoAdvanced filter: benefit names such as "health insurance", "401k" or "parental leave"; a job qualifies only when it states every listed benefit. Names that match no known benefit are ignored.
locationNoGeographic location (e.g., 'Boston, MA')
companiesNoFilter: official company names; a job from any of them qualifies, across every job board each employer posts on. More than one company makes it an advanced filter. Next to company, a job has to match both; hiring_brand narrows company only.
educationNoFilter: jobs whose posting requires one of these education levels (no_requirements, high_school, associate_degree, bachelor_degree, professional_certificate, postgraduate_degree); bachelor_degree means the posting asks for a bachelor degree, not that it suits someone holding one.
min_matchNoAdvanced filter: lowest personal FoundRole match grade to keep, the same letter each job shows in insights.match.grade. A and A- are rare even for a strong resume; B keeps good and strong matches; C+ also keeps fair ones. Needs a resume on the account.
work_modesNoAdvanced filter: jobs in any of these work modes (on_site, remote, hybrid). remote is matched across the whole country of the location, the others within the radius. ["remote"] is the same search as remote: true.
bonuses_onlyNoAdvanced filter: only jobs that state a bonus (sign-on, performance, referral, commission and the like).
hiring_brandNoFilter: one brand inside the company, for example company "Google" with hiring_brand "YouTube"; used only together with company.
salary_floorNoAdvanced filter: minimum annualized salary in USD; a posting qualifies when the lower bound of its pay band reaches the floor. Jobs without a USD salary are dropped.
strict_remoteNoAdvanced filter: only postings checked as fully remote that can be worked from the requested location: the posting names that area, allows anywhere, or does not say where. Stricter than remote; work_modes other than remote do not apply with it.
posted_days_agoNoNumber of days ago to search for jobs (1-365)
employment_typesNoFilter: jobs offered as any of these employment types (full_time, part_time, contractor, temporary, intern, volunteer, per_diem, other).
hide_low_qualityNoAdvanced filter: hides postings with a risky ghost grade (D/F); ungraded postings stay.
exclude_companiesNoAdvanced filter: official company names whose jobs are removed from the results, across every job board each employer posts on.
experience_levelsNoFilter: jobs at any of these experience levels (entry_level, mid_level, senior_level, executive). The level comes from the years of experience the posting asks for and the seniority in its title, the higher of the two; entry_level never includes a posting asking for more than two years.
h1b_sponsors_onlyNoAdvanced filter: only companies known to sponsor H1B visas.
confirmed_work_fromNoAdvanced filter: with strict_remote, also leaves out postings that do not say where the work can be done from.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
jobsNo
previewNo
feedKindNo
nextPageNo
feedStatusNo
totalCountNo
continueUrlNo
jobSearchIdNo
resultSetIdNo
statusOrderNo
revalidatingNo
resultBatchIdNo
trackerWebUrlNo
profileSetupUrlNo
profileSetupStateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed30 schema fields changedv1.1.16
    • addedInput schema / properties / benefits
      Added value: +{
      +  "description": "Advanced filter: benefit names such as \"health insurance\", \"401k\" or \"parental leave\"; a job qualifies only when it states every listed benefit. Names that match no known benefit are ignored.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • addedInput schema / properties / bonuses_only
      Added value: +{
      +  "description": "Advanced filter: only jobs that state a bonus (sign-on, performance, referral, commission and the like).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / companies
      Added value: +{
      +  "description": "Filter: official company names; a job from any of them qualifies, across every job board each employer posts on. More than one company makes it an advanced filter. Next to company, a job has to match both; hiring_brand narrows company only.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / company
      Added value: +{
      +  "description": "The official company name",
      +  "type": "string"
      +}
    • addedInput schema / properties / confirmed_work_from
      Added value: +{
      +  "description": "Advanced filter: with strict_remote, also leaves out postings that do not say where the work can be done from.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / education
      Added value: +{
      +  "description": "Filter: jobs whose posting requires one of these education levels (no_requirements, high_school, associate_degree, bachelor_degree, professional_certificate, postgraduate_degree); bachelor_degree means the posting asks for a bachelor degree, not that it suits someone holding one.",
      +  "items": {
      +    "enum": [
      +      "no_requirements",
      +      "high_school",
      +      "associate_degree",
      +      "bachelor_degree",
      +      "professional_certificate",
      +      "postgraduate_degree"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / employment_types
      Added value: +{
      +  "description": "Filter: jobs offered as any of these employment types (full_time, part_time, contractor, temporary, intern, volunteer, per_diem, other).",
      +  "items": {
      +    "enum": [
      +      "full_time",
      +      "part_time",
      +      "contractor",
      +      "temporary",
      +      "intern",
      +      "volunteer",
      +      "per_diem",
      +      "other"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / exclude_companies
      Added value: +{
      +  "description": "Advanced filter: official company names whose jobs are removed from the results, across every job board each employer posts on.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / experience_levels
      Added value: +{
      +  "description": "Filter: jobs at any of these experience levels (entry_level, mid_level, senior_level, executive). The level comes from the years of experience the posting asks for and the seniority in its title, the higher of the two; entry_level never includes a posting asking for more than two years.",
      +  "items": {
      +    "enum": [
      +      "entry_level",
      +      "mid_level",
      +      "senior_level",
      +      "executive"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / h1b_sponsors_only
      Added value: +{
      +  "description": "Advanced filter: only companies known to sponsor H1B visas.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hide_low_quality
      Added value: +{
      +  "description": "Advanced filter: hides postings with a risky ghost grade (D/F); ungraded postings stay.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / hiring_brand
      Added value: +{
      +  "description": "Filter: one brand inside the company, for example company \"Google\" with hiring_brand \"YouTube\"; used only together with company.",
      +  "type": "string"
      +}
    • changedInput schema / properties / location / description
      Previous value: -"Optional preferred location name or slug"New value: +"Geographic location (e.g., 'Boston, MA')"
    • addedInput schema / properties / min_match
      Added value: +{
      +  "description": "Advanced filter: lowest personal FoundRole match grade to keep, the same letter each job shows in insights.match.grade. A and A- are rare even for a strong resume; B keeps good and strong matches; C+ also keeps fair ones. Needs a resume on the account.",
      +  "enum": [
      +    "A",
      +    "A-",
      +    "B+",
      +    "B",
      +    "B-",
      +    "C+",
      +    "C"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / posted_days_ago
      Added value: +{
      +  "description": "Number of days ago to search for jobs (1-365)",
      +  "maximum": 365,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "The full job title or skill (e.g., \"Ruby Developer\", NOT just \"Ruby\")",
      +  "type": "string"
      +}
    • addedInput schema / properties / radius
      Added value: +{
      +  "description": "Search radius in miles around a city location (default 40); not used for state, country or remote searches.",
      +  "maximum": 100,
      +  "minimum": 5,
      +  "type": "integer"
      +}
    • addedInput schema / properties / remote
      Added value: +{
      +  "description": "Advanced filter: only remote-eligible jobs, matched across the whole country of the requested location rather than its radius.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / salary_floor
      Added value: +{
      +  "description": "Advanced filter: minimum annualized salary in USD; a posting qualifies when the lower bound of its pay band reaches the floor. Jobs without a USD salary are dropped.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Result order (score, posted_at, match, salary): score is relevance and the default, posted_at is newest first, salary is highest pay first, match is best personal fit first and needs a resume. Ordering by salary or match is an advanced option.",
      +  "enum": [
      +    "score",
      +    "posted_at",
      +    "match",
      +    "salary"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / strict_remote
      Added value: +{
      +  "description": "Advanced filter: only postings checked as fully remote that can be worked from the requested location: the posting names that area, allows anywhere, or does not say where. Stricter than remote; work_modes other than remote do not apply with it.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / work_modes
      Added value: +{
      +  "description": "Advanced filter: jobs in any of these work modes (on_site, remote, hybrid). remote is matched across the whole country of the location, the others within the radius. [\"remote\"] is the same search as remote: true.",
      +  "items": {
      +    "enum": [
      +      "on_site",
      +      "remote",
      +      "hybrid"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / continueUrl
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / jobs / items / properties / estimatedSalary / properties / basedOn
      Removed value: -{
      -  "type": [
      -    "string",
      -    "null"
      -  ]
      -}
    • addedOutput schema / properties / jobs / items / properties / estimatedSalary / properties / currency
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / jobs / items / properties / related
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / jobs / items / properties / resultItemId
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / preview
      Added value: +{
      +  "properties": {
      +    "continueUrl": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "hidden": {
      +      "type": "integer"
      +    },
      +    "hiddenAtLeast": {
      +      "type": "boolean"
      +    },
      +    "shown": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": [
      +    "object",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / resultBatchId
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / resultSetId
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observedv1.1.9

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: results are fit-ranked, may include related roles, carry the same insights payload as search, and free vs Pro accounts receive different result completeness (preview plus hidden count vs the full filtered list). It also documents the asynchronous processing status and that a later call returns the completed feed, which the annotations (idempotent, non-destructive, closed-world) do not convey.

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

Conciseness4/5

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

Front-loads the core purpose, then ambient behavior (ranking, insights), then tiering, then the jobs_search fallback and pagination/status semantics. Three compact paragraphs with little waste, though slightly longer than strictly needed for a read-style tool.

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?

With an output schema present, return values need not be described, and the description covers the remaining gaps an agent needs: what determines the feed, tier-gated completeness, async processing, pagination continuity, and the fallback search path. Nothing material for correct invocation is missing.

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% across 23 params, so the schema carries the per-parameter burden (baseline 3). The description still adds non-obvious parameter behavior: the search filters and sort apply to the personalized feed, and advanced parameters change output scope by account tier, which the schema does not state.

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?

Names a specific verb and resource — returns the authenticated user's personalized job recommendations — and states the inputs that build them (resume, skills, target roles, preferred location). It also distinguishes itself from jobs_search by explaining the fallback path when an explicit query names a different or unrecognized profession.

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?

Gives explicit routing: an explicit query outside the profile's target roles routes to the same general search as jobs_search rather than substituting the profile. It also notes how pages retrieve more of the same feed and what a processing status means. It stops short of stating outright when to prefer this over jobs_search for a normal query.

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