Skip to main content
Glama

Update Autofill Profile

set_autofill_profile
DestructiveIdempotent

Save application-form answers to the user's autofill profile, including personal details, preferences, education, languages, custom answers, and work permits, so the Companion can fill job forms.

Instructions

Save the user's application-form answers: the profile get_autofill_profile reads and the Companion fills forms from. Only the sections passed change. Inside personal, eligibility, preferences and each country's work-permit and own answers only the keys passed change, and a null removes one; education and languages replace the stored list whole (get_autofill_profile returns them). Each custom answer replaces the saved one with the same question (case and spacing ignored) and the same only_for and only_for_kind, or is added: for an answer held for one company or city, send its only_for and only_for_kind as get_autofill_profile shows them, or a second scoped answer is added. A saved answer is never removed here, so one the Companion learned meanwhile stays (removing one is the user's, in Profile). A work-permit answer is per country and a form question without one is asked on that form, never defaulted; setup counts the answers of each country in apply_in (set_markets). Diversity (EEO) answers have no field here: they and their consent are the user's, in Profile. An unknown section, key or market key writes nothing, nor does a status outside its market's list, a country answer that market does not ask or a citizenship that names no country (the refusal names what is allowed). Returns {profile, setup}: the saved profile without eeo (current pay only while the user lets the Companion fill agreements), and setup status's form-answer readiness (readiness 0 to 1, groups, blocking, work_auth_by_country counts, chosen), null when that read fails.

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": "set_autofill_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
customNo
personalNo
educationNo
languagesNo
eligibilityNo
preferencesNo
answers_by_countryNoEach country's own answers by market key, merged like the work permits. On that country's jobs each fills its form slot (expected_pay over preferences.desired_salary), so pay in a country's own terms (monthly, CTC) belongs here, not in preferences. Once countries are chosen, a country with no expected_pay gets no pay on its forms (the Companion asks), and the home country's expected_pay is saved as preferences.desired_salary, so a read never lists it here; an entry left with nothing reads as {}.
work_auth_by_countryNoWork-permit answers by market key. Each country's answers merge key by key; a country set to null loses its answers; a country left out keeps them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.14.0
    • addedInput schema / $defs / CountryAnswers
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "One country's own answers (true is Yes); a null removes one. A market takes only the ones it asks: get_autofill_profile's questions list each market's in its words, and a refused save names them.",
      +  "properties": {
      +    "current_ctc": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Current Ctc"
      +    },
      +    "expected_pay": {
      +      "anyOf": [
      +        {
      +          "type": "string"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Expected Pay"
      +    },
      +    "in_country_now": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "In Country Now"
      +    },
      +    "uae_driving_licence": {
      +      "anyOf": [
      +        {
      +          "type": "boolean"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ],
      +      "title": "Uae Driving Licence"
      +    }
      +  },
      +  "title": "CountryAnswers",
      +  "type": "object"
      +}
    • changedInput schema / $defs / EligibilityAnswers / description
      Previous value: -"Yes/No eligibility answers (true is Yes); a null removes one."New value: +"Yes/No eligibility answers (true is Yes), and total work experience as whole years plus\nthe months beyond them (0 to 11); a null removes one."
    • addedInput schema / $defs / EligibilityAnswers / properties / experience_months
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 11,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Experience Months"
      +}
    • addedInput schema / $defs / EligibilityAnswers / properties / experience_years
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maximum": 60,
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Experience Years"
      +}
    • changedInput schema / $defs / LanguageEntry / description
      Previous value: -"One language; native and fluent are separate answers, as forms ask them."New value: +"One language; native and fluent are separate answers, as forms ask them, and cefr is its\nCEFR level."
    • addedInput schema / $defs / LanguageEntry / properties / cefr
      Added value: +{
      +  "enum": [
      +    "A1",
      +    "A2",
      +    "B1",
      +    "B2",
      +    "C1",
      +    "C2"
      +  ],
      +  "title": "Cefr",
      +  "type": "string"
      +}
    • changedInput schema / $defs / PersonalAnswers / description
      Previous value: -"Contact and address answers; a null removes one."New value: +"Contact and address answers, and citizenships: the countries the user is a citizen of, as\nISO codes (\"IN\") or English names, stored as codes (get_autofill_profile shows names); a null\nremoves one."
    • addedInput schema / $defs / PersonalAnswers / properties / citizenships
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Citizenships"
      +}
    • changedInput schema / $defs / PreferenceAnswers / description
      Previous value: -"Start and pay answers, in the words a form gets; a null removes one."New value: +"Start and pay answers, in the words a form gets; a null removes one. desired_salary is the\npay of the country the user lives in once they chose their countries (each other country's is\nanswers_by_country[market].expected_pay; a home entry sent there is saved here), and the one\nfigure for every country while none is chosen. notice_days is the notice period in whole days,\nthe one notice answer; notice_period text such as \"2 weeks\" is read as days; text that says\nnone (\"negotiable\") is kept only while no days are stored (send notice_days: null with it);\nforms get the days in words. last_working_day is\nYYYY-MM-DD, filled while serving_notice is true and the day has not passed;\npreferred_locations is cities separated by commas."
    • addedInput schema / $defs / PreferenceAnswers / properties / last_working_day
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Last Working Day"
      +}
    • addedInput schema / $defs / PreferenceAnswers / properties / notice_days
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Notice Days"
      +}
    • addedInput schema / $defs / PreferenceAnswers / properties / preferred_locations
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Preferred Locations"
      +}
    • addedInput schema / $defs / PreferenceAnswers / properties / serving_notice
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "title": "Serving Notice"
      +}
    • changedInput schema / $defs / WorkPermitAnswers / description
      Previous value: -"One country's work-permit answers (true is Yes); a null removes one. status is the US\nvisa status, asked for the US only; authorization_expires_on is YYYY-MM-DD, absent when the\nright to work there does not run out."New value: +"One country's work-permit answers (true is Yes); a null removes one. status is one of that\nmarket's own statuses (get_autofill_profile's questions list each market's, and a refused\nsave names them; a market with no list takes none); authorization_expires_on is YYYY-MM-DD,\nabsent when the right to work there does not run out."
    • changedInput schema / $defs / WorkPermitAnswers / properties / status / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "citizen",
      -      "permanent_resident",
      -      "opt",
      -      "stem_opt",
      -      "h1b",
      -      "tn",
      -      "other_visa",
      -      "not_authorized"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / answers_by_country
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "anyOf": [
      +          {
      +            "$ref": "#/$defs/CountryAnswers"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "propertyNames": {
      +        "enum": [
      +          "US",
      +          "UK",
      +          "CA",
      +          "AU",
      +          "IE",
      +          "IN",
      +          "DE",
      +          "NL",
      +          "AE"
      +        ]
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Each country's own answers by market key, merged like the work permits. On that country's jobs each fills its form slot (expected_pay over preferences.desired_salary), so pay in a country's own terms (monthly, CTC) belongs here, not in preferences. Once countries are chosen, a country with no expected_pay gets no pay on its forms (the Companion asks), and the home country's expected_pay is saved as preferences.desired_salary, so a read never lists it here; an entry left with nothing reads as {}.",
      +  "title": "Answers By Country"
      +}
    • changedInput schema / properties / work_auth_by_country / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {
      -      "anyOf": [
      -        {
      -          "$ref": "#/$defs/WorkPermitAnswers"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "propertyNames": {
      -      "enum": [
      -        "US",
      -        "UK",
      -        "CA",
      -        "AU",
      -        "IE",
      -        "IN",
      -        "DE",
      -        "NL"
      -      ]
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {
      +      "anyOf": [
      +        {
      +          "$ref": "#/$defs/WorkPermitAnswers"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "propertyNames": {
      +      "enum": [
      +        "US",
      +        "UK",
      +        "CA",
      +        "AU",
      +        "IE",
      +        "IN",
      +        "DE",
      +        "NL",
      +        "AE"
      +      ]
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Addedv0.12.0

TDQS

A4.4/5.0
Behavior5/5

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

Far exceeds the annotations by disclosing merge semantics per section (key-by-key with null removal for personal/eligibility/preferences, whole-list replacement for education and languages), refusal conditions ("An unknown section, key or market key writes nothing"), and the custom-answer dedupe rule. It also explains why the destructiveHint=true profile applies (list replacement) while asserting explicit removals are out of scope.

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

Conciseness3/5

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

Purpose is front-loaded, but the body is one dense run-on block with nested parentheticals and repeated clauses ("as get_autofill_profile shows them" and "a refused save names them" appear twice). The content mostly earns its place, yet headers or bullets would make the per-section merge rules far easier to apply.

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 an eight-parameter mutation with no output schema, coverage is strong: it describes the returned {profile, setup} shape, refusals, and the interaction with set_markets' apply_in counting. Missing are authorization/permission expectations and how errors are surfaced beyond the refusal naming what is allowed.

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?

With schema description coverage at 25%, the description compensates well: it explains per-section merge behavior, the special role of only_for/only_for_kind in custom answers, and the country scoping of work permits. It does not enumerate most individual keys, relying on the $defs titles for those.

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?

Opens with a specific verb and resource: "Save the user's application-form answers," then anchors the resource to its reader ("the profile get_autofill_profile reads and the Companion fills forms from"). This lets an agent separate it from sibling writers like set_markets or set_job_preferences without opening the schema.

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?

Gives clear context on scope ("Only the sections passed change") and explicit exclusions: "A saved answer is never removed here... removing one is the user's, in Profile" and "Diversity (EEO) answers have no field here." It lacks an explicit statement of when to prefer it over nearby writers such as set_job_preferences or update_application.

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

Deploy Server

Other Tools