Skip to main content
Glama

AIApply

Save the AIApply job setup

save_auto_apply_setup
Idempotent

Use this once the user has seen and confirmed the job titles, location, work mode, job type and experience level AIApply needs: call it with confirmed=true and the values they confirmed, without asking them again. Without confirmed it only checks the values and saves nothing. Only for a first setup — once saved, preferences are changed in AIApply, never here. After it saves, call get_setup_status for the next step. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one. It also needs a permission the user grants; if it was not granted, calling it asks the user to allow it.

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": {
      "job_titles": "<job_titles>",
      "country": "<country>",
      "work_mode": "<work_mode>",
      "work_type": "<work_type>",
      "experience_level": "<experience_level>"
    },
    "name": "save_auto_apply_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional: narrow the search to this city in that country.
countryYesThe country to work in, as a name or ISO code. WW for remote anywhere.
confirmedNoTrue only after the user has confirmed these exact values.
work_modeYesin_person_hybrid for on-site or hybrid, full_remote for remote.
work_typeYes
job_titlesYes1 to 5 roles to apply for.
experience_levelYes

Output Schema

NameRequiredDescriptionDefault
fieldNoThe field to fix, when one was refused.
savedNoTrue when the setup was saved.
reasonNoWhy nothing was saved, when nothing was.
valuesNoThe values as they are, or will be, saved.
appliedNo
messageYes
searchingNoWhether AIApply now searches for this user.
user_messageNoShow this to the user rather than message.
dashboard_urlNoThe AIApply dashboard, where the user manages Auto Apply.
updates_offerNoPresent once, when the account is first ready: something you may offer the user. Act on it only if they agree.
preferences_urlNo
finish_setup_urlNo
search_only_ends_atNoWhen AIApply stops searching for this account, if it searches without applying.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (which already declare non-read-only, idempotent, non-destructive), the description discloses the dry-run behavior when confirmed is absent, the account requirement, and the permission-grant requirement with what happens when each is missing. It also states the one-time nature of the call, which an agent could not infer from annotations alone.

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?

The key instruction (call with confirmed=true after user confirmation) is front-loaded and every sentence carries operational content. It is a dense single block, and the confirmed/dry-run point is restated twice, which costs a little tightness.

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?

Output schema exists, so return values need not be described. For a 7-parameter write tool with auth and permission gating, the description covers prerequisites, dry-run semantics, the one-time constraint, and the next step — nothing material is missing.

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 71%, and the description adds genuine meaning for the most consequential parameter: confirmed=true means the user has already confirmed these exact values, and omitting it makes the call validation-only. It does not clarify the work_type array or experience_level enum values, but those are enumerated in the schema.

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?

The description names a specific verb+resource (save the AIApply job setup) and scopes it to 'once the user has seen and confirmed' the five fields. It also clearly separates this from sibling operations: saving here is only for first setup, while later preference changes happen in AIApply and status checks go to get_setup_status.

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?

It gives explicit when-to-use ('once the user has seen and confirmed... call it with confirmed=true... without asking them again'), when-not ('Only for a first setup — once saved, preferences are changed in AIApply, never here'), and the follow-up action ('After it saves, call get_setup_status'). This is unusually complete routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources