AI Applyd

Optimize Resume with AI

aiapplyd_optimize_resume

Rewrite a resume so it passes ATS screening. Returns the rewritten resume, a projected ATS score, and an itemised summary of every change made.

Instructions

Rewrite a resume so it passes ATS screening. Returns the rewritten resume, a projected ATS score, and an itemised summary of every change made. Pass job_description to tailor the rewrite to one specific posting, or omit it for general ATS optimization. Requires a connected AI Applyd account. Uses the user's AI credits. Do not use it to apply: aiapplyd_apply tailors the resume for every application on its own. resume_text is optional: the user can paste or attach a resume in the chat, and you pass its text as resume_text. Without it, the tool uses the resume already on the user's account. In ChatGPT the user can attach a resume file; pass it as resume_file.

Input Schema

TableJSON Schema

Name	Required	Description
`resume_file`	No	In ChatGPT the user can attach a resume file; pass it as resume_file. It is downloaded once, right away: PDF, DOCX or plain text, up to 10 MB.
`resume_text`	No	Full text of the resume to optimize. The resume the user pasted or attached in this conversation, as plain text. Omit it to use the resume already on the user's AI Applyd account.
`job_description`	No	Full text of the target job description (optional, omit for general ATS optimization)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`changes`	Yes
`optimizedResume`	Yes
`projectedAtsScore`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.9.0Oct 14, 2026

addedInput schema / properties / resume_file

Added value: +{
+  "additionalProperties": false,
+  "description": "In ChatGPT the user can attach a resume file; pass it as resume_file. It is downloaded once, right away: PDF, DOCX or plain text, up to 10 MB.",
+  "properties": {
+    "download_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "file_id": {
+      "type": "string"
+    },
+    "file_name": {
+      "type": "string"
+    },
+    "mime_type": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "download_url",
+    "file_id"
+  ],
+  "type": "object"
+}

changedInput schema / properties / resume_text / description

Previous value: -"Full text of the resume to optimize"New value: +"Full text of the resume to optimize. The resume the user pasted or attached in this conversation, as plain text. Omit it to use the resume already on the user's AI Applyd account."

removedInput schema / required
```
Removed value: -[
-  "resume_text"
-]
```

Changed2 schema fields changedv1.8.5Oct 12, 2026
- removedOutput schema / properties / projectedAtsScore / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / projectedAtsScore / type
```
Added value: +[
+  "number",
+  "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": {
+    "changes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "optimizedResume": {
+      "type": "string"
+    },
+    "projectedAtsScore": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "optimizedResume",
+    "changes",
+    "projectedAtsScore"
+  ],
+  "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?

Goes beyond the annotations by disclosing the account requirement and that the call consumes the user's AI credits, plus what the response contains. It does not clarify whether the rewritten resume replaces the resume stored on the account, which matters given readOnlyHint=false and idempotentHint=false.

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 purpose and return payload, then routing rules, then prerequisites and the anti-sibling warning. Slightly redundant with the schema's own resume_file/resume_text descriptions, but every sentence carries usable instruction.

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 it needn't explain return format, and it covers the three optional params and the account/credit prerequisites well. The remaining gap is whether the account resume is mutated or merely read, which is material for a non-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?

Schema coverage is 100%, so the baseline is 3, but the description adds real routing semantics: job_description changes the optimization mode, resume_text accepts chat-pasted or attached text, and resume_file is the ChatGPT attachment path with the account fallback when omitted.

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 ('Rewrite a resume so it passes ATS screening') and enumerates the return payload (rewritten resume, projected ATS score, itemised change summary). It explicitly distinguishes itself from the nearest sibling: 'Do not use it to apply: aiapplyd_apply tailors the resume for every application on its own.'

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 conditional routing: pass job_description to tailor to one posting, omit for general optimization; resume_text optional with fallback to the account resume; resume_file for ChatGPT attachments. It also states the exclusion against aiapplyd_apply and names prerequisites (connected AI Applyd account).

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