Skip to main content
Glama

AIApply

Open AIApply job preferences

open_auto_apply_preferences
Read-onlyIdempotent

Use this when the connected user asks to change their AIApply job preferences — target roles, locations, work types, experience, salary, excluded companies, the daily limit, or how applications are submitted. Nothing here can change them: this returns the link to the page where the user changes them themselves. Read the current values with get_auto_apply_preferences first, tell the user what would change, then give them this link. Never say a preference has been changed. 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": "open_auto_apply_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
viewYes
messageYes
preferences_urlYesThe AIApply page where the user changes their preferences.

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?

Annotations already flag readOnlyHint/idempotentHint, but the description adds the decisive behaviour an annotation cannot convey: the call returns a URL rather than performing a change, and the agent must not claim a preference was changed. It also discloses the authentication behaviour — an unsigned-in user is prompted to sign in or create an account — which is exactly the kind of side effect that matters for an apparently read-only call.

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 trigger condition, then capability boundary, then ordered procedure, then auth caveat — every sentence carries a distinct job. It is slightly dense at four sentences and the 'Never say a preference has been changed' warning could be folded into the workflow sentence, but nothing is redundant.

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-only link-opener with an output schema present, the description covers everything an agent needs: when to call it, what it returns, the prerequisite read step, the auth path, and the user-facing phrasing constraint. Nothing material is left to inference.

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 no argument semantics to document and the baseline is 4. The description correctly avoids inventing parameter talk and instead spends its words on behaviour.

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?

Names a specific verb and resource ('open ... job preferences') and immediately bounds the scope: 'Nothing here can change them: this returns the link to the page where the user changes them themselves.' That distinguishes it cleanly from the sibling that reads the same data (get_auto_apply_preferences) and from any save/update tool.

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 ('when the connected user asks to change their AIApply job preferences'), an enumerated set of preference topics it covers, and a prescribed workflow: read with get_auto_apply_preferences first, state what would change, then hand over the link. It also supplies an exclusion ('nothing here can change them') so the agent knows not to promise a mutation.

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