AI Applyd

Get Account

aiapplyd_get_account

Read-onlyIdempotent

Instructions

Show the user's AI Applyd account: plan, token balance, applications left in the current 30-day window, the job preferences their matches are found against, and readiness: whether a resume is on file, whether setup is finished, and which profile fields employer forms require that are still empty. Also lists their resumes, the default apply mode, and whether Gmail, Outlook and Indeed are connected. Call it before applying to several jobs. Read-only: it spends no credits and changes nothing. Do not use it to change anything; use aiapplyd_update_job_preferences, aiapplyd_update_application_profile or aiapplyd_set_resume. Next: aiapplyd_set_resume when no resume is on file, otherwise aiapplyd_get_matches. To turn auto-apply on or off or change its mode, use aiapplyd_update_auto_apply.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`plan`	Yes
`resumes`	Yes
`autopilot`	Yes	Whether AI Applyd applies on its own. Read only.
`readiness`	Yes
`billingUrl`	Yes
`preferences`	Yes
`applications`	Yes
`integrations`	Yes	Which outside accounts are connected. Null when it could not be read.
`tokenBalance`	Yes
`defaultApplyMode`	Yes	What aiapplyd_apply does when mode is omitted. Read only.
`freeApplications`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.9.0Oct 14, 2026

addedOutput schema / properties / integrations

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "connectUrl": {
+          "description": "Dashboard page where the user connects or reconnects these accounts. Connecting needs the provider's own sign-in in a browser.",
+          "type": "string"
+        },
+        "gmail": {
+          "additionalProperties": false,
+          "properties": {
+            "connected": {
+              "description": "True when AI Applyd can use this account now.",
+              "type": "boolean"
+            },
+            "email": {
+              "description": "The connected account's address.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "status": {
+              "description": "The recorded state, such as connected, needs_reconnect, signing_in, waiting_for_phone_code or failed. Null when it was never connected.",
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "connected",
+            "status",
+            "email"
+          ],
+          "type": "object"
+        },
+        "indeed": {
+          "additionalProperties": false,
+          "properties": {
+            "connected": {
+              "description": "True when AI Applyd can use this account now.",
+              "type": "boolean"
+            },
+            "email": {
+              "description": "The connected account's address.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "status": {
+              "description": "The recorded state, such as connected, needs_reconnect, signing_in, waiting_for_phone_code or failed. Null when it was never connected.",
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "connected",
+            "status",
+            "email"
+          ],
+          "type": "object"
+        },
+        "outlook": {
+          "additionalProperties": false,
+          "properties": {
+            "connected": {
+              "description": "True when AI Applyd can use this account now.",
+              "type": "boolean"
+            },
+            "email": {
+              "description": "The connected account's address.",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "status": {
+              "description": "The recorded state, such as connected, needs_reconnect, signing_in, waiting_for_phone_code or failed. Null when it was never connected.",
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "required": [
+            "connected",
+            "status",
+            "email"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "gmail",
+        "outlook",
+        "indeed",
+        "connectUrl"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Which outside accounts are connected. Null when it could not be read."
+}

changedOutput schema / required

Previous value: -[
-  "plan",
-  "tokenBalance",
-  "applications",
-  "freeApplications",
-  "preferences",
-  "readiness",
-  "resumes",
-  "defaultApplyMode",
-  "autopilot",
-  "billingUrl"
-]New value: +[
+  "plan",
+  "tokenBalance",
+  "applications",
+  "freeApplications",
+  "preferences",
+  "readiness",
+  "resumes",
+  "defaultApplyMode",
+  "autopilot",
+  "billingUrl",
+  "integrations"
+]

Changed8 schema fields changedv1.8.5Oct 12, 2026

changedOutput schema / properties / plan / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "currentPeriodEnd": {
-        "type": "string"
-      },
-      "endsAt": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "interval": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "status": {
-        "type": "string"
-      },
-      "tier": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "name",
-      "tier",
-      "status",
-      "interval",
-      "currentPeriodEnd",
-      "endsAt"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "currentPeriodEnd": {
+        "type": "string"
+      },
+      "endsAt": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "interval": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "status": {
+        "type": "string"
+      },
+      "tier": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "required": [
+      "name",
+      "tier",
+      "status",
+      "interval",
+      "currentPeriodEnd",
+      "endsAt"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / readiness / properties / onboardingComplete / anyOf

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

addedOutput schema / properties / readiness / properties / onboardingComplete / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedOutput schema / properties / readiness / properties / resumeOnFile / anyOf

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

addedOutput schema / properties / readiness / properties / resumeOnFile / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

changedOutput schema / properties / resumes / anyOf

Previous value: -[
-  {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "id": {
-          "description": "Pass to aiapplyd_set_resume as document_id to make it the base resume.",
-          "type": "number"
-        },
-        "isBase": {
-          "type": "boolean"
-        },
-        "title": {
-          "type": "string"
-        },
-        "updatedAt": {
-          "anyOf": [
-            {
-              "type": "string"
-            },
-            {
-              "type": "null"
-            }
-          ]
-        }
-      },
-      "required": [
-        "id",
-        "title",
-        "isBase",
-        "updatedAt"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "description": "Pass to aiapplyd_set_resume as document_id to make it the base resume.",
+          "type": "number"
+        },
+        "isBase": {
+          "type": "boolean"
+        },
+        "title": {
+          "type": "string"
+        },
+        "updatedAt": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "id",
+        "title",
+        "isBase",
+        "updatedAt"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / tokenBalance / anyOf

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

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

Addedv1.8.0Sep 25, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, but the description adds the credit-cost model ('it spends no credits'), which annotations cannot express. It also discloses readiness gating (resume on file, setup finished, missing profile fields), which is genuinely actionable behavioral context beyond the schema.

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 resource and its contents, then usage, exclusions and next steps in logical order. Slightly repetitive: 'changes nothing' and 'Do not use it to change anything' restate the same read-only guarantee, costing a few words.

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?

An output schema exists, so the description does not need to explain return values, and the empty parameter set needs no documentation. What remains — when to call, what it protects (credits), and where to go next — is fully covered for a simple read-only tool.

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 and the schema is an empty object with 100% coverage, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly avoids inventing parameter semantics.

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+resource ('Show the user's AI Applyd account') and then enumerates exactly what the account view contains: plan, token balance, remaining applications, job preferences, readiness signals, resumes, apply mode and connected inboxes. This makes it instantly separable from siblings like get_matches or get_applications.

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 when ('Call it before applying to several jobs'), explicit when-not ('Do not use it to change anything'), and names the three mutation alternatives with their exact conditions. It also routes forward: set_resume when no resume is on file, otherwise get_matches, and update_auto_apply for auto-apply changes.

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