AI Applyd

Auto Apply to Job

aiapplyd_auto_apply

Destructive

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 (Greenhouse, Lever, Ashby, Workday, iCIMS, Personio, Teamtailor, SmartRecruiters, Recruitee, Breezy, Workable, Rippling, BambooHR, JazzHR, softgarden, Jobvite, Gem, Zoho Recruit, Dayforce, Hireology, Dover, Oracle, Paylocity, UKG Pro Recruiting, ADP, Avature, CareerPlug, Pinpoint, Manatal, Eightfold, BrassRing, SAP SuccessFactors, Polymer, and Paycom), 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.

Changed18 schema fields changedv1.8.5Oct 12, 2026

removedOutput schema / properties / applicationId / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / applicationId / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / company / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / company / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / jobMatchId / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / jobMatchId / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / jobTitle / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / jobTitle / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / jobUrl / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / jobUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / preparationStatus / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / preparationStatus / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / recordedMode / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / recordedMode / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / trackingUrl / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / trackingUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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.2/5.0

Behavior4/5

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

Annotations already declare destructive=true, readOnly=false, idempotent=false, openWorld=true, so the safety profile is covered. The description still adds real context: it applies on the employer's own hiring system, respects the account's review setting, and 'spends one of the user's applications' — a cost/consequence not expressed in any structured field.

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?

The deprecation notice and the cost statement are correctly front-loaded and earn their place, but the enumeration of ~30 ATS platform names consumes roughly half the text without helping the agent decide or invoke. Trimming the list would sharpen the definition considerably.

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?

With an output schema present, annotations covering the safety profile, and a single 100%-documented parameter, the description only needed to add deprecation routing, scope, and side effects — all of which it does. Little is missing apart from any hint about failure modes on unsupported employers.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents job_url fully. The description restates that application is keyed by job_url but adds no format, validation, or edge-case detail beyond the schema, which is the baseline-3 case.

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?

Front-loads the deprecation status and the replacement tool by name, then states a specific verb+resource: applies to ONE job posting by job_url, end to end. An agent can distinguish it from aiapplyd_apply and from read-only siblings without opening any 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?

Explicitly instructs 'use aiapplyd_apply' instead, which is the clearest possible when-to-use / when-not-to-use guidance. It also states the operative condition that the behavior 'follows the account's review setting', so the agent knows the call may not submit immediately.

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