AI Applyd

Auto Apply to Job

aiapplyd_auto_apply

Destructive

Submit an application to one job posting by URL directly on the employer's ATS (Workday, Greenhouse, Lever, etc.), following your account's review settings and consuming one application credit.

Instructions

Deprecated alias of aiapplyd_apply, use aiapplyd_apply. Applies to ONE job posting by job_url, end to end, on the employer's own hiring system (Workday, Greenhouse, Lever, Ashby, Workable, iCIMS, Personio, Recruitee, Teamtailor, Rippling, Breezy, SmartRecruiters, BambooHR, JazzHR, softgarden), following the account's review setting. Spends one of the user's applications.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_url`	Yes	URL of the job posting to apply to

Output Schema

TableJSON Schema

Name	Required	Description
`jobUrl`	Yes
`status`	Yes	Our own record. Never proof the employer received it.
`company`	Yes
`outcome`	Yes	started: a new application; already_in_progress: this job already had one (alreadyExisted); not_confirmed: the user declined, nothing was sent.
`jobTitle`	Yes
`jobMatchId`	Yes
`trackingUrl`	Yes
`recordedMode`	Yes
`applicationId`	Yes	The application to follow with aiapplyd_get_applications. Null only when nothing was started.
`requestedMode`	Yes
`alreadyExisted`	Yes	True when this job already had an application, which is returned instead of a second one.
`preparationStatus`	Yes
`preparedUnderFreeWatch`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.8.0Sep 25, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "alreadyExisted": {
+      "description": "True when this job already had an application, which is returned instead of a second one.",
+      "type": "boolean"
+    },
+    "applicationId": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The application to follow with aiapplyd_get_applications. Null only when nothing was started."
+    },
+    "company": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "jobMatchId": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "jobTitle": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "jobUrl": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "outcome": {
+      "description": "started: a new application; already_in_progress: this job already had one (alreadyExisted); not_confirmed: the user declined, nothing was sent.",
+      "enum": [
+        "started",
+        "already_in_progress",
+        "not_confirmed"
+      ],
+      "type": "string"
+    },
+    "preparationStatus": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "preparedUnderFreeWatch": {
+      "type": "boolean"
+    },
+    "recordedMode": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "requestedMode": {
+      "anyOf": [
+        {
+          "enum": [
+            "auto_approve",
+            "copilot"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "status": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Our own record. Never proof the employer received it."
+    },
+    "trackingUrl": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "outcome",
+    "applicationId",
+    "jobMatchId",
+    "jobTitle",
+    "company",
+    "jobUrl",
+    "requestedMode",
+    "recordedMode",
+    "status",
+    "preparationStatus",
+    "preparedUnderFreeWatch",
+    "alreadyExisted",
+    "trackingUrl"
+  ],
+  "type": "object"
+}

First observedv1.3.0Sep 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already establish that this is destructive and not read-only; the description adds meaningful context by stating it 'spends one of the user's applications' and by scoping the action to one job posting across listed ATS systems. It does not cover auth or rate limits, but the key consequence is disclosed.

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?

The deprecation warning is front-loaded, and every subsequent clause carries operational meaning: one job, end-to-end, supported systems, review setting, and cost. The ATS list is long but directly tells an agent where the tool works, so no sentence is wasted.

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 one-parameter tool with an output schema and rich annotations, this description covers the essential operational facts: what is acted on, the supported contexts, the review behavior, and the irreversible cost. Nothing needed to decide whether to invoke it is missing.

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

Parameters3/5

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

Schema coverage is 100% and the single job_url parameter is already documented as 'URL of the job posting to apply to.' The description reinforces that the URL selects a single job, but it adds no format, normalization, or other parameter-level detail beyond 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 states a concrete action ('applies to ONE job posting by job_url, end to end') and identifies the target resource, and it explicitly distinguishes itself from aiapplyd_apply by declaring itself a deprecated alias. This leaves no ambiguity about what the tool does or which sibling should be used.

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 opens with an explicit directive: 'Deprecated alias of aiapplyd_apply, use aiapplyd_apply.' It also specifies when the underlying behavior applies (one job URL, on the employer's own ATS, following the review setting), so an agent knows both the alternative and the conditions around use.

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

Deploy Server