Skip to main content
Glama

Update Job Preferences

getmattered_update_job_preferences
DestructiveIdempotent

Update saved job titles, locations, salary, and work styles for GetMattered job matching, then re-run the search. Lists replace saved values; add_target_roles and add_locations append instead.

Instructions

Changes the job titles, locations and other preferences GetMattered searches for, then searches again. Lists replace what is saved; add_target_roles and add_locations add to it.

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_update_job_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
pausedNoTrue pauses new matches for the user; false resumes them. It never changes auto-apply.
job_typesNoJob types to match.
locationsNoFull list of locations to search in.
salary_maxNoHighest yearly salary to target, in salary_currency.
salary_minNoLowest yearly salary the user accepts, in salary_currency (e.g. 120000).
descriptionNoWhat the user wants, in their own words (e.g. "remote only, 120k+, senior, no crypto"). Fields passed explicitly win over it. Uses AI credits.
remote_onlyNoDeprecated name of include_remote, with the same meaning.
work_stylesNoWork styles to match.
target_rolesNoFull list of job titles to search for.
add_locationsNoLocations to add (e.g. "San Francisco, CA"). The saved locations stay.
include_remoteNoWhether remote jobs in the user's region are included alongside their locations.
salary_currencyNoCurrency of the salary band (default usd).
add_target_rolesNoJob titles to add. The saved titles stay.
experience_levelsNoSeniority levels to match.
exclude_industriesNoIndustries to never match (e.g. ["Crypto"]).
application_answersNoAnswers for employer forms, saved to the user's application profile as getmattered_update_application_profile saves them. Each is a value the user stated, never a guess.
needs_visa_sponsorshipNoTrue when the user needs visa sponsorship to take the job.

Output Schema

NameRequiredDescriptionDefault
pausedYes
jobTypesYes
locationsYes
salaryMaxYes
salaryMinYes
workStylesYes
targetRolesYes
includeRemoteYes
salaryCurrencyYes
remoteWorldwideYes
visaSponsorshipYes
describedSummaryYesHow GetMattered understood `description`, when one was given.
experienceLevelsYes
excludeIndustriesYes
onboardingCompletedYesTrue when this call finished the account setup, so GetMattered starts searching for these roles.
applicationAnswersSavedYesThe application_answers fields written to the application profile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.20.1
    • changedInput schema / properties / add_locations / description
      Previous value: -"Locations to add to the saved list (e.g. \"San Francisco, CA\"). The saved locations stay."New value: +"Locations to add (e.g. \"San Francisco, CA\"). The saved locations stay."
    • changedInput schema / properties / add_target_roles / description
      Previous value: -"Job titles to add to the saved list. The saved titles stay."New value: +"Job titles to add. The saved titles stay."
    • changedInput schema / properties / application_answers / description
      Previous value: -"Answers employer forms ask for, saved to the user's application profile: phone, city, state, zip_code, country, linkedin_url, work_authorization, willing_to_relocate, available_start_date, notice_period. Each holds a value the user stated, never a guess."New value: +"Answers for employer forms, saved to the user's application profile as getmattered_update_application_profile saves them. Each is a value the user stated, never a guess."
    • changedInput schema / properties / exclude_industries / description
      Previous value: -"Industries to never match (e.g. [\"Crypto\"]). REPLACES the saved list."New value: +"Industries to never match (e.g. [\"Crypto\"])."
    • changedInput schema / properties / experience_levels / description
      Previous value: -"Seniority to match: intern, entry, junior, mid, senior, lead, executive. REPLACES the saved list."New value: +"Seniority levels to match."
    • changedInput schema / properties / job_types / description
      Previous value: -"Job types to match: full_time, part_time, contract, internship, freelance, temporary. REPLACES the saved list."New value: +"Job types to match."
    • changedInput schema / properties / locations / description
      Previous value: -"Full list of locations to search in. REPLACES the saved list. add_locations adds to the saved list and keeps it."New value: +"Full list of locations to search in."
    • changedInput schema / properties / target_roles / description
      Previous value: -"Full list of job titles to hunt for. REPLACES the saved list. add_target_roles adds to the saved list and keeps it."New value: +"Full list of job titles to search for."
    • changedInput schema / properties / work_styles / description
      Previous value: -"Work styles to match: onsite, hybrid, remote. REPLACES the saved list."New value: +"Work styles to match."
  2. Changed4 schema fields changedv1.18.0
    • addedInput schema / properties / add_locations
      Added value: +{
      +  "description": "Locations to add to the saved list (e.g. \"San Francisco, CA\"). The saved locations stay.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / add_target_roles
      Added value: +{
      +  "description": "Job titles to add to the saved list. The saved titles stay.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / locations / description
      Previous value: -"Full list of locations to search in. REPLACES the saved list."New value: +"Full list of locations to search in. REPLACES the saved list. add_locations adds to the saved list and keeps it."
    • changedInput schema / properties / target_roles / description
      Previous value: -"Full list of job titles to hunt for. REPLACES the saved list."New value: +"Full list of job titles to hunt for. REPLACES the saved list. add_target_roles adds to the saved list and keeps it."
  3. Changed4 schema fields changedv1.13.2
    • changedInput schema / properties / application_answers / description
      Previous value: -"Answers employer forms ask for, saved to the user's application profile: phone, city, state, zip_code, country, linkedin_url, work_authorization, willing_to_relocate, available_start_date, notice_period. Only values the user stated, never guesses."New value: +"Answers employer forms ask for, saved to the user's application profile: phone, city, state, zip_code, country, linkedin_url, work_authorization, willing_to_relocate, available_start_date, notice_period. Each holds a value the user stated, never a guess."
    • changedInput schema / properties / include_remote / description
      Previous value: -"Include remote jobs in the user's region alongside their locations."New value: +"Whether remote jobs in the user's region are included alongside their locations."
    • changedInput schema / properties / locations / description
      Previous value: -"Full list of preferred locations. REPLACES the saved list."New value: +"Full list of locations to search in. REPLACES the saved list."
    • changedInput schema / properties / remote_only / description
      Previous value: -"Deprecated name of include_remote. Use include_remote."New value: +"Deprecated name of include_remote, with the same meaning."
  4. Addedv1.9.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real context: an update triggers a fresh search, and full lists overwrite saved values while add_* variants preserve them. That overwrite warning is exactly the behavioral detail a destructive write tool needs. It does not mention credit consumption or what happens to unspecified preferences.

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

Conciseness5/5

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

Two sentences, zero filler. The core action and its re-search consequence are front-loaded, and the replace/add rule follows immediately where an agent needs it while filling the schema.

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

Completeness4/5

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

With 17 parameters, a nested application_answers object, and an output schema, the description is concise but covers the highest-risk semantic (overwrite vs append) and the re-search side effect. Edge behaviors such as paused/auto-apply interaction and AI-credit cost are only in the schema, but they are covered there and in the output schema.

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

Parameters3/5

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

Schema coverage is 100%, so each of the 17 parameters is already documented, including the replace/add distinction in the individual field descriptions. The description restates the list-vs-add contrast at a cross-parameter level but adds no syntax, defaults, or precedence detail beyond the schema (the AI-credits and precedence notes live in the schema itself).

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

Purpose4/5

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

The description gives a specific verb ("changes") and resource (job titles, locations and other search preferences) plus a notable side effect ("then searches again"). It distinguishes the tool from read-only siblings such as get_matches, but names no competing write sibling (e.g. update_saved_search) to sharpen the boundary.

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

Usage Guidelines3/5

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

It clearly explains the replace-vs-append choice between full lists and add_target_roles/add_locations, which is genuine usage guidance. It gives no when-to-use or when-not-to-use guidance relative to sibling tools like update_saved_search or update_automatic_apply_settings, so the agent must infer the routing.

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