Get Job Matches
getmattered_get_matchesRead-onlyIdempotent
Searches the user's job matches: the open roles that fit their resume and preferences, best fit first and mixed across companies, so scores are not in strict order. Also reads full postings by job_match_ids or job_url. Scores run 0 to 100. An empty list means the search is still running or found nothing, or askUserFor names a missing resume or target roles. On a new account, nextStep names the first step. Changes nothing and spends nothing.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "getmattered_get_matches"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, starting at 1 (e.g. 2 for the next page) | |
| limit | No | Matches per page, 1 to 50 (default 10) | |
| query | No | Narrows the user's existing matches to titles containing this text (e.g. "Product Designer"). It does not search for new jobs; getmattered_update_job_preferences changes the roles GetMattered searches for. | |
| job_url | No | Link to any job posting, read without saving it, one link per call. The answer also says whether GetMattered can apply there. getmattered_apply reads a posting itself, and every read counts toward the same limit. | |
| location | No | Narrows the user's existing matches to this place (e.g. "San Francisco, CA", "New York", "Remote"). It does not search for new jobs; getmattered_update_job_preferences changes the locations GetMattered searches. | |
| saved_only | No | If true, the list holds only the matches the user saved | |
| remote_only | No | If true, the list holds only remote-friendly positions | |
| job_match_ids | No | Matches to read in full: up to 10 job_match_ids (e.g. [48213]). Returns the full posting, skills, benefits and work arrangement. | |
| after_job_match_id | No | Limits the list to matches newer than this job_match_id, such as the newestJobMatchId of an earlier answer. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| mode | Yes | ||
| page | Yes | ||
| matches | Yes | ||
| posting | Yes | A posting read from job_url. Nothing was saved. A null title means the link could not be read as a posting: applySupport and hiringSystem still hold, and nextStep says what to do. | |
| nextStep | Yes | The open next step, when there is one: the empty list's missing step, applications waiting for review, the offer to apply to the best matches, or a short list. | |
| setupStep | No | Present while account setup is open: the first setup step. | |
| askUserFor | Yes | Filled when the list is empty because the account still needs something from the user: resume or target_roles. | |
| totalPages | Yes | ||
| notFoundIds | Yes | Requested job_match_ids with no match on this account. | |
| offeredApply | Yes | True when this answer offers to apply to the jobs in offeredJobMatchIds on one yes from the user. | |
| totalMatches | Yes | ||
| newestJobMatchId | Yes | The highest job_match_id on this page. As after_job_match_id on a later call, it limits the list to newer matches. | |
| offeredJobMatchIds | Yes | The jobs the offer names, best fit first, ready as getmattered_apply job_match_ids. Empty when nothing is offered. |