set_filtersSave a partial filter change. Omitted fields stay unchanged; empty category strings clear them. Origin is a coordinate pair; home is its display label.
| Name | Required | Description | Default |
|---|---|---|---|
| filters | Yes |
Changes observed during successful MCP inspections.
Input schema / properties / filters / properties / origin / descriptionPrevious value: -"Driving start coordinates. Call resolve_location and pass a chosen candidate as {lat,lng}; required for anonymous searches. Null clears a saved origin."New value: +"Driving start coordinates. Coordinates as {lat,lng}; required for anonymous searches. Null clears a saved origin."Input schema / properties / filters / properties / function / descriptionPrevious value: -"Function code from get_filter_options; empty string clears."New value: +"Function code from get_filter_options, or several comma-separated to match any of them; empty string clears."Input schema / properties / filters / properties / function / maxLengthPrevious value: -40New value: +400Input schema / properties / filters / properties / industry / descriptionPrevious value: -"Industry code from get_filter_options; empty string clears."New value: +"Industry code from get_filter_options, or several comma-separated to match any of them; empty string clears."Input schema / properties / filters / properties / industry / maxLengthPrevious value: -40New value: +400Input schema / properties / filters / properties / level / descriptionPrevious value: -"Seniority inferred from title and experience; empty string clears."New value: +"Seniority inferred from title and experience: intern, entry, mid, senior, manager or director, or several comma-separated to match any of them; empty string clears."Input schema / properties / filters / properties / level / enumRemoved value: -[
- "",
- "intern",
- "entry",
- "mid",
- "senior",
- "manager",
- "director"
-]Input schema / properties / filters / properties / level / maxLengthAdded value: +100Input schema / properties / filters / properties / level / patternAdded value: +"^((intern|entry|mid|senior|manager|director)(,(intern|entry|mid|senior|manager|director))*)?$"Input schema / properties / filters / properties / sort / descriptionPrevious value: -"Shortest commute, newest first, or highest annualized pay first; default commute."New value: +"Closest (shortest commute), newest first, or highest annualized pay first; default commute."Input schema / properties / filters / properties / max_minutes / descriptionPrevious value: -"Maximum one-way driving minutes, excluding live traffic; default 20."New value: +"Maximum one-way driving minutes; default 20."Input schema / properties / filters / properties / function / descriptionAdded value: +"Function code from get_filter_options; empty string clears."Input schema / properties / filters / properties / home / descriptionAdded value: +"Display label only; never geocoded. Pass origin coordinates to search."Input schema / properties / filters / properties / include_near_misses / descriptionAdded value: +"Include routed jobs up to 1.5 times max_minutes; default false."Input schema / properties / filters / properties / include_no_pay / descriptionAdded value: +"Include unknown pay when min_pay is set; default true."Input schema / properties / filters / properties / industry / descriptionAdded value: +"Industry code from get_filter_options; empty string clears."Input schema / properties / filters / properties / level / descriptionAdded value: +"Seniority inferred from title and experience; empty string clears."Input schema / properties / filters / properties / max_minutes / descriptionAdded value: +"Maximum one-way driving minutes, excluding live traffic; default 20."Input schema / properties / filters / properties / min_pay / descriptionAdded value: +"Minimum annual USD pay, using posted range midpoint and 2080 hours/year; 0 clears."Input schema / properties / filters / properties / origin / descriptionAdded value: +"Driving start coordinates. Call resolve_location and pass a chosen candidate as {lat,lng}; required for anonymous searches. Null clears a saved origin."Input schema / properties / filters / properties / query / descriptionAdded value: +"Title/company words or related occupation titles; empty string clears."Input schema / properties / filters / properties / saved_only / descriptionAdded value: +"Intersect results with account bookmarks; requires jobs:read; default false."Input schema / properties / filters / properties / sort / descriptionAdded value: +"Shortest commute, newest first, or highest annualized pay first; default commute."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description usefully explains the merge semantics behind destructiveHint=true (omitted fields unchanged, empty strings clear), which annotations alone cannot convey. However it leaves the biggest behavioral question open: whether the change persists to a saved search record or only affects transient search state, and whether it is scoped to the caller's account.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core action and free of padding. It could have spent one of those sentences on scope instead of repeating the origin/home distinction from the schema.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The nested schema is rich and annotations cover the safety profile, so the description does not need to enumerate fields. What it still omits is the target of the mutation and its relationship to search_jobs/update_search — a material gap for a destructive, non-read-only tool with no output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Reported coverage is 0% because the single top-level "filters" property is undocumented, but every nested field carries a detailed description, so the schema does most of the work. The description's only parameter detail ("Origin is a coordinate pair; home is its display label") restates what the nested schema already says verbatim; the genuinely additive piece is the global merge/clear rule.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
"Save a partial filter change" gives a verb and resource, but never says what the filters belong to — the current session, a named saved search, or global state. With siblings like get_filters, save_search, update_search and search_jobs, an agent cannot tell from the description which filter surface this mutates.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use or when-not-to-use guidance is given, and no sibling is named. The partial-merge rule hints at PATCH-style usage but does not say when to call set_filters instead of search_jobs, save_search or update_search.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.