AI Applyd

Build Resume

aiapplyd_build_pdf

Build a formatted, ATS-clean resume from raw text in the user's AI Applyd resume builder, where it stays editable and downloads as a PDF. Templates: modern, classic, or minimal. Private to the account by default; set make_public to true only if the user explicitly asks for a shareable public link. Requires a paid plan (Hired in 30+).

Input Schema

TableJSON Schema

Name	Required	Description
`template`	No	Resume template style (default: classic)
`make_public`	No	Publish a public share link. Anyone with the link sees the resume INCLUDING its contact details. Defaults to false (private). Only set true when the user explicitly asks to share it.
`resume_text`	Yes	Full text of the resume

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedAug 29, 2026

removedInput schema / properties / locale

Removed value: -{
-  "description": "Language for the human-readable parts of the answer: en, es, de, fr or pt-BR. Defaults to the language this connection was opened in. Machine fields (ids, URLs, scores) never change.",
-  "enum": [
-    "en",
-    "es",
-    "de",
-    "fr",
-    "pt-BR"
-  ],
-  "type": "string"
-}

Changed1 schema field changedAug 29, 2026

addedInput schema / properties / locale

Added value: +{
+  "description": "Language for the human-readable parts of the answer: en, es, de, fr or pt-BR. Defaults to the language this connection was opened in. Machine fields (ids, URLs, scores) never change.",
+  "enum": [
+    "en",
+    "es",
+    "de",
+    "fr",
+    "pt-BR"
+  ],
+  "type": "string"
+}

AddedJul 14, 2026

TDQS

A4.3/5.0

Behavior5/5

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

The description discloses several behavioral traits beyond the annotations: the resume remains editable, downloads as a PDF, defaults to private with make_public only when explicitly requested, and requires a paid plan. This adds meaningful context about side effects (public link creation) and prerequisites not covered by the annotations. No contradiction with any annotation.

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?

The description is four sentences, front-loaded with the primary purpose, and each sentence carries meaningful information (output format, templates, privacy, paid plan). No filler or redundant content, though it could be slightly more compact.

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?

No output schema exists, so the description must clarify the return value. It says 'downloads as a PDF,' which implies a PDF output, but it does not specify whether the tool returns a link, binary content, or a confirmation. Overall, it covers the essential context for invocation, including side effects and requirements.

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%, so the baseline is 3. The description repeats the template enum and the make_public privacy behavior, but these are already fully described in the schema. It adds minimal extra meaning beyond what the schema provides, so a score of 3 is appropriate.

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 states a specific action: 'Build a formatted, ATS-clean resume from raw text' in the user's AI Applyd resume builder, with output as an editable PDF. It clearly distinguishes itself from sibling tools like optimize_resume or score_resume by focusing on the build/format action and PDF generation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context on when to use the tool—for building a resume from raw text with a choice of templates, and it notes the paid plan requirement and privacy default. It does not explicitly name alternative tools or state 'when not to use,' but the context is unambiguous enough for an agent.

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

All AI Applyd tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool maps cleanly to a distinct job-search action: analyze a posting, apply, build/optimize/score/translate resumes, generate cover letters/interview prep, search jobs, and update preferences. The only adjacent pair, score_resume and optimize_resume, is clearly separated by assessment versus rewrite.

Naming Consistency5/5

All tools share a consistent aiapplyd_ prefix and follow an actionable verb_noun pattern: analyze_job_description, generate_cover_letter, score_resume, update_job_preferences. No style mixing or vague generic names are present.

Tool Count5/5

Ten tools is well-scoped for a job-application assistant, covering the main user journeys without redundancy or bloat. Each tool has a clear, non-overlapping responsibility.

Completeness4/5

The tool surface covers the core lifecycle: preferences, job search, resume analysis and optimization, PDF generation, cover letters, auto-apply, and interview prep. Minor gaps exist around listing saved resumes/cover letters and tracking submitted applications, but these are workable via the connected account.

Resources

Need Help?