AI Applyd

Analyze Job Description

aiapplyd_analyze_job_description

Instructions

Extract the ATS keywords and requirements in a job posting, with each term's category, importance and must-have flag. Shows must-have versus nice-to-have requirements so the resume can reflect 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?

Annotations only cover readOnly/idempotent/openWorld hints; the description adds meaningful context they don't: the tool requires a connected AI Applyd account and consumes the user's AI credits, and it explains what is extracted. It stops short of describing pagination, limits, or failures, but for a short analysis call this is strong added value.

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?

Four tight sentences, each earning its place: what it does, why it matters, a prerequisite/cost note, an exclusion with alternative, and next steps. Information is front-loaded with no 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?

With an output schema present, return values need not be explained, and the description covers the practical essentials: account/credit requirements, the read-from-link exclusion, and the recommended follow-up tools. Nothing an agent needs to select or call it 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 coverage is 100% with a single well-documented 'job_description' parameter, so the schema already carries the semantics. The description adds nothing about length limits or expected format, so the baseline 3 applies.

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?

Specific verb (extract) plus resource (ATS keywords and requirements from a job posting) and it details the output shape (category, importance, must-have flag). It is clearly separable from sibling tools like get_matches and 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?

Explicitly states when-not-to-use ('Do not use it to read a posting from a link; use aiapplyd_get_matches with job_url') and names the alternative. It also spells out the follow-on tools (score_resume/optimize_resume) with the same input, giving a full routing path.

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