AI Applyd

Analyze Job Description

aiapplyd_analyze_job_description

Analyze a job description to identify ATS keywords, required vs preferred skills, seniority signals, and red flags before tailoring your resume.

Instructions

Extract what a job posting actually screens on: the exact ATS keywords, must-have versus nice-to-have requirements, seniority signals, and red flags. Call this before tailoring a resume so the resume mirrors the posting's own language. Requires a connected AI Applyd account and uses the user's AI credits. Do not use it to read a posting from a link; use aiapplyd_get_matches with job_url. Next: aiapplyd_score_resume or aiapplyd_optimize_resume with the same job description.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`job_description`	Yes	Full text of the job description

Output Schema

TableJSON Schema

Name	Required	Description	Default
`keywords`	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": {
+    "keywords": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "category": {
+            "type": "string"
+          },
+          "importance": {
+            "type": "number"
+          },
+          "mustHave": {
+            "type": "boolean"
+          },
+          "term": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "term",
+          "category",
+          "importance",
+          "mustHave"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "keywords"
+  ],
+  "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?

Beyond the annotations, the description discloses meaningful operational context: it requires a connected AI Applyd account and consumes the user's AI credits. It does not contradict the annotations, and while it doesn't detail all side effects, the added auth and cost information is useful.

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 description is four sentences with no filler. The primary purpose is front-loaded, followed by usage timing, an exclusion with the correct alternative, and next-step recommendations—all in a compact, scannable structure.

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 single-parameter analysis tool with an output schema and annotations, the description covers purpose, when to use, when not to use, alternatives, required account state, and cost implications. Nothing essential for correct invocation 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 description coverage is 100%, and the only parameter, job_description, is already documented as 'Full text of the job description' in the schema. The tool description doesn't add much parameter-specific meaning beyond that, which matches the baseline for high schema coverage.

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 opens with a specific verb and resource: 'Extract what a job posting actually screens on,' and enumerates concrete outputs (ATS keywords, must-have versus nice-to-have requirements, seniority signals, red flags). This clearly distinguishes it from sibling tools like aiapplyd_get_matches and aiapplyd_score_resume.

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 explicitly says when to call it ('Call this before tailoring a resume'), what not to use it for ('Do not use it to read a posting from a link'), and names the alternative (aiapplyd_get_matches with job_url). It also chains the next steps by recommending aiapplyd_score_resume or aiapplyd_optimize_resume afterward.

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

Deploy Server