AI Applyd

Score Resume

aiapplyd_score_resume

Score a resume for ATS compatibility. Returns an overall score, section scores, the keywords the resume matches and the ones it is missing, and specific rewrite suggestions.

Instructions

Score a resume for ATS compatibility. Returns an overall score, section scores, the keywords the resume matches and the ones it is missing, and specific rewrite suggestions. Pass job_description to score against a posting, or omit it for a general ATS readiness score. Requires a connected AI Applyd account and uses the user's credits. Do not use it to rewrite the resume; use aiapplyd_optimize_resume. Next: aiapplyd_optimize_resume rewrites the resume against the same posting. 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. 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 job description (optional, omit for a general ATS readiness score)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`suggestions`	Yes
`overallScore`	Yes
`sectionScores`	Yes
`keywordMatches`	Yes
`missingKeywords`	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"New value: +"Full text of the resume. 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.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": {
+    "keywordMatches": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "missingKeywords": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "overallScore": {
+      "type": "number"
+    },
+    "sectionScores": {
+      "additionalProperties": false,
+      "properties": {
+        "education": {
+          "type": "number"
+        },
+        "experience": {
+          "type": "number"
+        },
+        "formatting": {
+          "type": "number"
+        },
+        "keywords": {
+          "type": "number"
+        },
+        "skills": {
+          "type": "number"
+        }
+      },
+      "required": [
+        "skills",
+        "experience",
+        "education",
+        "formatting",
+        "keywords"
+      ],
+      "type": "object"
+    },
+    "suggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "overallScore",
+    "sectionScores",
+    "keywordMatches",
+    "missingKeywords",
+    "suggestions"
+  ],
+  "type": "object"
+}

First observedv1.3.0Sep 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=false, idempotentHint=false, destructiveHint=false; the description supplies the non-obvious behavioral facts the agent actually needs — a connected AI Applyd account is required and the call consumes the user's credits. It does not state whether re-scoring is charged again or how failures are reported, so it stops short of a 5.

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 contents, then usage conditions, then parameter guidance — a sensible order. It loses a little efficiency by referencing aiapplyd_optimize_resume twice ('Do not use it to rewrite...' and 'Next: aiapplyd_optimize_resume rewrites...'), which is mild redundancy rather than filler.

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 return values need not be explained, and the description still summarizes them. With account/credit prerequisites, the optional job_description mode, and the three resume input paths all covered for a zero-required-parameter tool, an agent has everything needed to call it correctly.

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 meaning: it explains the resume_text fallback ('Without it, the tool uses the resume already on the user's account') and the ChatGPT attach path for resume_file. The interaction between resume_text, resume_file and the stored account resume is the key semantic the schema alone cannot convey.

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 and resource ('Score a resume for ATS compatibility') and immediately enumerates the return contents (overall score, section scores, matched/missing keywords, rewrite suggestions). It also explicitly distinguishes itself from the sibling aiapplyd_optimize_resume, so an agent can route correctly without opening either 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?

Gives explicit conditional usage: 'Pass job_description to score against a posting, or omit it for a general ATS readiness score.' It names the when-not case ('Do not use it to rewrite the resume; use aiapplyd_optimize_resume') and even suggests the next step, leaving no routing ambiguity.

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