Skip to main content
Glama

Save settings and résumé

freeapply_update_settings
DestructiveIdempotent

Change your FreeApply settings: save facts and preferences, résumé text and profile, or the AI models used for scans. Overwrites only the fields you send, with no undo.

Instructions

Changes the user's settings: facts and preferences the user states, the résumé's text and profile (setup), and the AI models scan. Reading: freeapply_get_settings; single form answers: freeapply_manage_answers. Use: when the user states a fact or preference, in setup's résumé step, in the AI models step. Never fill a field the user didn't give you. Behavior: overwrites the sent fields, no undo. Deep merge: only sent fields change, nested objects merge, lists are replaced whole. User-only sections (legal, sharing, automation, autorun, onboarding, integrity, model_choices) are skipped and listed in ignored. All or nothing: one wrong field saves nothing. Parameters: patch, nested by section with the names freeapply_get_settings returns, e.g. {"targets": {"min_pay": 60000}}. Writable: profile, targets, eligibility, cover_letter, custom_answers (one at a time: freeapply_manage_answers), gmail (not last_check or manual_logins); resume only text and profile {headline, skills, titles, education, certifications}, taken from the résumé text alone; models only the scan {app, current, can_delegate, available, efforts}, read from your own tools, which replaces the last one. Returns: {changed, ignored, setup_complete, missing}; after a scan also models (model and effort chosen per level). Errors: nothing writable, unknown section or field, wrong type, value outside its choices (e.g. cover_letter.length short|standard|long), résumé files (the user adds them in the dashboard), malformed scan; the message names every problem.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "patch": "<patch>"
    },
    "name": "freeapply_update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYesFields to change, nested by section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.6
    • changedInput schema / properties / patch / description
      Previous value: -"Fields to change, nested by section with freeapply_get_settings' names, e.g. {\"targets\": {\"min_pay\": 60000}}. resume: only text and profile {headline, skills, titles, education, certifications}, from the résumé text alone. models: the scan {app, current, can_delegate, available, efforts}, read from your own tools; replaces the last scan."New value: +"Fields to change, nested by section."
  2. Changed1 schema field changedv1.0.4
    • changedInput schema / properties / patch / description
      Previous value: -"The fields to change, nested by section, e.g. {\"profile\": {\"phone\": \"+1 555 0100\"}}."New value: +"Fields to change, nested by section with freeapply_get_settings' names, e.g. {\"targets\": {\"min_pay\": 60000}}. resume: only text and profile {headline, skills, titles, education, certifications}, from the résumé text alone. models: the scan {app, current, can_delegate, available, efforts}, read from your own tools; replaces the last scan."
  3. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / patch / description
      Previous value: -"The fields to change, nested by section, e.g. {\"targets\": {\"min_pay\": 60000, \"locations\": [\"Denver, CO\"]}} or {\"profile\": {\"phone\": \"+1 555 0100\"}}. Field names are as freeapply_get_settings returns them."New value: +"The fields to change, nested by section, e.g. {\"profile\": {\"phone\": \"+1 555 0100\"}}."
  4. Changed1 schema field changedv1.0.1
    • addedInput schema / properties / patch / description
      Added value: +"The fields to change, nested by section, e.g. {\"targets\": {\"min_pay\": 60000, \"locations\": [\"Denver, CO\"]}} or {\"profile\": {\"phone\": \"+1 555 0100\"}}. Field names are as freeapply_get_settings returns them."
  5. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark it destructive and idempotent, and the description adds substantial operational context: overwrites without undo, deep-merge semantics, whole-list replacement, skipped user-only sections listed in ignored, and all-or-nothing saves. It also describes error behavior where the message names every problem.

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?

It is dense but organized into clear operational clauses: Changes, Use, Behavior, Parameters, Returns, and Errors. The purpose and usage are front-loaded, and each section carries distinct information needed for a complex nested update tool rather than repeating structured fields.

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?

For a destructive nested update tool with no output schema, the description covers return fields (changed, ignored, setup_complete, missing, and models after a scan) and the main error cases. Combined with merge and skipped-section behavior, it is complete enough for an agent to invoke it correctly.

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

Parameters5/5

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

The schema only says patch is an object nested by section. The description supplies the actual section names, an example patch, the writable fields, résumé and model-scan restrictions, and validation constraints such as cover_letter.length choices, which is far beyond what the schema provides.

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 the specific resource (user settings) and the three content areas it saves: stated facts/preferences, résumé text and profile, and the AI model scan. It also names freeapply_get_settings for reading and freeapply_manage_answers for single form answers, distinguishing it from those siblings.

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?

Explicitly says when to use it: when the user states a fact or preference, during setup's résumé step, or in the AI models step. It also gives a clear when-not rule: never fill a field the user did not provide, and routes reading to freeapply_get_settings and single answers to freeapply_manage_answers.

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