AI Applyd

Update Auto Apply

aiapplyd_update_auto_apply

DestructiveIdempotent

Instructions

Change the user's Auto Apply settings: turn it on or off (enabled), and set the default apply mode, the daily limit and the lowest match it applies to. While Auto Apply is on, AI Applyd starts applications every day without a swipe. default_apply_mode "auto" sends them to the employer under the user's name without asking first, and a sent application cannot be undone. "review" prepares each one and holds it for approval. The default apply mode is also what aiapplyd_apply does when its mode is omitted. Call it only when the user asks to change these settings, never on your own. Turning Auto Apply on needs the Hired Yesterday plan; on another plan the answer says so and nothing changes. Returns the settings after the change. Do not use it to apply to one job; use aiapplyd_apply. Next: aiapplyd_get_applications to follow what Auto Apply starts.

Input Schema

TableJSON Schema

Name	Required	Description
`enabled`	No	true turns Auto Apply on, false turns it off. Omit to leave it as it is.
`daily_limit`	No	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.
`match_level`	No	Lowest match Auto Apply applies to: "excellent" (90+), "strong" (80+), "good" (70+) or "stretch" (60+). Omit to leave it as it is.
`default_apply_mode`	No	"auto": applications go to the employer without asking first. "review": each one waits for the user's approval. Also the mode aiapplyd_apply uses when its mode is omitted. Omit to leave it as it is.

Output Schema

TableJSON Schema

Name	Required	Description
`changed`	Yes	The settings this call asked to change.
`settings`	Yes	The settings after the change. Null when the user declined the confirmation.
`notConfirmed`	Yes	True when the user declined the confirmation and nothing changed.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.9.0Oct 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations declare non-readonly, destructive, idempotent, open-world, but the description adds substantial context they cannot convey: the Hired Yesterday plan prerequisite, that a failed plan check changes nothing, that "auto" mode sends immediately and cannot be undone, and that the returned payload is the settings. This goes well beyond the annotations.

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-loaded with the core action, then behavior, then guardrails and routing. It is dense and long, but nearly every sentence carries distinct information; a small trim of the redundant mode explanation would be possible without losing meaning.

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?

An output schema exists, so return values need not be described; the description still notes that it returns the settings. All four optional parameters, their omission semantics, the plan gate, and the sibling routing are covered, leaving nothing an agent needs to call it correctly.

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% and enums are self-documented, so the baseline is 3. The description adds genuine cross-parameter meaning by explaining that default_apply_mode is also the mode aiapplyd_apply falls back to when omitted, 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?

States a specific verb (change/update) and resource (Auto Apply settings), then enumerates exactly which settings (enabled, apply mode, daily limit, match level). It clearly distinguishes itself from aiapplyd_apply and aiapplyd_auto_apply by naming what it is not for.

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

Usage Guidelines5/5

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

Explicit trigger (only when the user asks to change these settings), explicit exclusion (never on your own), names the alternative tool for the adjacent task (aiapplyd_apply for a single application), and states a next step (aiapplyd_get_applications). Nothing is left to inference.

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