Skip to main content
Glama

Update Auto Apply Settings

getmattered_update_automatic_apply_settings
DestructiveIdempotent

Turn Auto Apply on or off and set its default mode, daily application limit, and lowest match level; enabling it requires the Hired Yesterday plan.

Instructions

Turns Auto Apply on or off and sets its default mode, daily limit and lowest match. While on, applications start without asking per job. Turning it on needs the Hired Yesterday plan.

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

Input Schema

NameRequiredDescriptionDefault
enabledNotrue turns Auto Apply on, false turns it off. Left out, it stays as it is.
daily_limitNoMost applications Auto Apply starts in a day. The plan's own daily cap can lower it. Left out, it stays as it is.
match_levelNoLowest match Auto Apply applies to: "excellent" (90+), "strong" (80+), "good" (70+) or "stretch" (60+). Left out, it stays as it is.
default_apply_modeNo"auto": applications go to the employer without asking first. "review": each one waits for the user's approval. Also the mode getmattered_apply uses when its mode is omitted. Left out, it stays as it is.

Output Schema

NameRequiredDescriptionDefault
changedYesThe settings this call asked to change.
settingsYesThe settings after the change. Null when the user declined the confirmation.
setupStepNoPresent while account setup is open: the first setup step.
notConfirmedYesTrue when the user declined the confirmation and nothing changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.20.1
    • changedInput schema / properties / daily_limit / description
      Previous value: -"Most applications Auto Apply starts in a day, 1 to 50. The plan's own daily cap can lower it. Left out, it stays as it is."New value: +"Most applications Auto Apply starts in a day. The plan's own daily cap can lower it. Left out, it stays as it is."
  2. Changed5 schema fields changedv1.13.2
    • changedInput schema / properties / daily_limit / description
      Previous value: -"Most applications Auto Apply starts in a day, 1 to 50. The plan's own daily cap can lower it. Omit to leave it as it is."New value: +"Most applications Auto Apply starts in a day, 1 to 50. The plan's own daily cap can lower it. Left out, it stays as it is."
    • changedInput schema / properties / default_apply_mode / description
      Previous value: -"\"auto\": applications go to the employer without asking first. \"review\": each one waits for the user's approval. Also the mode getmattered_apply uses when its mode is omitted. Omit to leave it as it is."New value: +"\"auto\": applications go to the employer without asking first. \"review\": each one waits for the user's approval. Also the mode getmattered_apply uses when its mode is omitted. Left out, it stays as it is."
    • changedInput schema / properties / enabled / description
      Previous value: -"true turns Auto Apply on, false turns it off. Omit to leave it as it is."New value: +"true turns Auto Apply on, false turns it off. Left out, it stays as it is."
    • changedInput schema / properties / match_level / description
      Previous value: -"Lowest match Auto Apply applies to: \"excellent\" (90+), \"strong\" (80+), \"good\" (70+) or \"stretch\" (60+). Omit to leave it as it is."New value: +"Lowest match Auto Apply applies to: \"excellent\" (90+), \"strong\" (80+), \"good\" (70+) or \"stretch\" (60+). Left out, it stays as it is."
    • addedOutput schema / properties / setupStep
      Added value: +{
      +  "description": "Present while account setup is open: the first setup step.",
      +  "type": "string"
      +}
  3. Addedv1.10.2

TDQS

A3.8/5.0
Behavior3/5

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

With destructiveHint=true and openWorldHint=true already declared, the description usefully explains what makes this destructive — enabling the mode causes applications to be submitted without per-job approval — and adds an entitlement requirement the annotations cannot convey. It stops short of saying whether turning the mode off halts already-queued applications or whether submitted applications can be recalled, which is the material risk for a destructive, open-world mutation.

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?

Three short sentences, each earning its place: the action first, then the runtime consequence, then the gating requirement. No filler or repetition of the identical title.

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?

For a four-parameter, all-optional mutation with full schema coverage, existing output schema and destructive/idempotent annotations, the description supplies the two things structured fields cannot: the user-visible effect and the plan prerequisite. The remaining gap is reversal behavior on disable, which keeps it from complete.

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 description coverage is 100% and each parameter already documents its enum values, 1–50 bound, plan-cap interaction and leave-it-unchanged default, so the schema carries the semantic load. The description only paraphrases the parameter set ('default mode, daily limit and lowest match') without adding new meaning, so the baseline 3 applies.

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 uses a specific verb and resource — turning Auto Apply on or off and configuring its default mode, daily limit and lowest match — so the agent knows exactly which settings change. It touches the adjacent getmattered_apply tool only indirectly (via the default mode), and does not explicitly contrast itself with the other update_* settings tools, so it falls short of full sibling differentiation.

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?

It gives real operating context (applications then start without asking per job) and a hard prerequisite (the Hired Yesterday plan), which tells the agent when the call will and will not succeed. It never states when not to use it or which sibling to call instead for job-preference or saved-search configuration.

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