Skip to main content
Glama

AIApply

Get AIApply job preferences

get_auto_apply_preferences
Read-onlyIdempotent

Use this when the connected user asks about current AIApply job preferences or before suggesting a change. Read target roles, locations, work types, experience, salary, exclusions, daily limit, and application mode without modifying them. Nothing here can change them: to change one, call open_auto_apply_preferences for the page the user changes it on. Needs an AIApply account: if the user has not signed in, calling it asks them to sign in or create one.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
viewYes
preferencesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the tool cannot mutate anything and redirects changes to another tool, and it requires an AIApply account, with a sign-in/create-account prompt triggered on unauthenticated calls. Only minor redundancy ('without modifying them' restated as 'Nothing here can change them') keeps it off a 5.

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 usage trigger, then the read-only constraint, then the account prerequisite. Three sentences, all earning their place, though the read-only point is made twice in near-identical wording and could be collapsed.

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 zero-parameter read tool with full annotation coverage and an output schema, the description covers everything an agent needs: when to call it, what it returns, that it cannot mutate, which sibling handles mutation, and the authentication prerequisite plus its failure behavior.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a no-param tool is 4. The field list in the description usefully signals what comes back rather than what goes in.

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 (read) and resource (AIApply job preferences) and enumerates the exact fields returned: target roles, locations, work types, experience, salary, exclusions, daily limit, application mode. It also distinguishes itself from the mutation path by naming open_auto_apply_preferences, so an agent can pick the right tool without opening a schema.

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?

Gives explicit triggering conditions (user asks about current preferences, or before suggesting a change) and an explicit alternative with the condition that selects it: to change a preference, call open_auto_apply_preferences instead. Both when-to-use and when-not-to-use are covered.

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