Skip to main content
Glama

AI Applyd

by io.github.whateverneveranywhere

Auto Apply to Job

aiapplyd_auto_apply
Destructive

Apply to ONE specific job posting end to end: the resume and cover letter are rewritten for that role, then the form is completed and submitted on the employer's own hiring system, not a job board. All fifteen major ATS platforms land: Workday, Greenhouse, Lever, Ashby, Workable, iCIMS, Personio, Recruitee, Teamtailor, Rippling, Breezy, SmartRecruiters, BambooHR, JazzHR, softgarden. Follows the account's review setting: submits directly, or routes to the review queue. Requires a paid plan (Hired in 30+).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_urlYesURL of the job posting to apply to

Schema Changelog

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

  1. Changed1 schema field changed
    • 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"
-}
  2. Changed1 schema field changed
    • 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"
+}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructive and not-idempotent behavior, and the description adds substantial context on top: it actually rewrites documents, submits the form on the employer's ATS, and either submits directly or routes to a review queue based on account settings. It also discloses the paid-plan prerequisite, a behavioral constraint not available in schema or annotations.

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?

Three sentences pack the core action, supported ATS platforms, review behavior, and pricing constraint without redundancy. The platform list is long but earns its place because compatibility is a valid decision input for the agent.

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 destructive, externally visible action with one input parameter, the description covers what will happen, where it happens, which platforms are supported, how review settings affect submission, and the required paid plan. Return values are not described, but no output schema exists and the agent has enough to select and invoke the tool 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?

The single parameter job_url has a schema description, and the tool description adds useful selection semantics by emphasizing 'ONE specific job posting' and 'not a job board'. This tells the agent to pass a direct employer ATS posting URL rather than an aggregator link, which the schema alone does not 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?

Opens with 'Apply to ONE specific job posting end to end', a specific verb and resource, and immediately distinguishes itself from sibling component-tools by covering the whole pipeline from rewriting to submission on the employer's own hiring system. The ATS list and review-queue behavior further pin down exactly what this tool does.

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 makes clear the tool is for applying to a single specific posting and not to a job-board listing, so an agent knows the right input context. It does not explicitly name sibling tools or say 'use X instead when you only want a cover letter/resume', but the scope is unambiguous enough for invocation.

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

All AI Applyd toolsInspect
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