Skip to main content
Glama

Write a tailored resume or cover letter for a tracked job

generateApplicationDocuments

Start writing a cover letter and/or a resume tailored to one tracked application, from its job description, and attach the PDFs to it. It runs in the background, about a minute per document; returns { runId, requestedAt } straight away. Then call getTailoredResume with the applicationId (changes and match score before and after) or listApplications (resumeUrl, coverLetterUrl) to see the result. A tailored resume whose updatedAt is before requestedAt is the earlier version, not this one; if nothing newer is there after three minutes, tell the candidate it didn't go through, usually the daily limit per document kind.

The application needs a job description; add one with updateApplication first if it has none. Only facts already on the candidate's Clera resume are used. Writing a new tailored resume replaces the earlier one for that application. applyToJob sends this tailored resume for that job.

Clera privately records this tool's inputs and results for usage tracking and support.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "applicationId": "<applicationId>",
      "kinds": "<kinds>"
    },
    "name": "generateApplicationDocuments"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsYescover_letter, resume, or both.
tailoringNoFor the resume only: how much to rewrite (strength), length (pageLimit) and bullets per role. Defaults when absent; set them only when the candidate asks.
applicationIdYesThe id from a listApplications or trackApplication result.

Output Schema

NameRequiredDescriptionDefault
runIdYes
requestedAtYes
applicationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare it as a non-read-only, non-idempotent, non-open-world write; the description goes well beyond by disclosing the async execution model (~a minute per document), the immediate { runId, requestedAt } return, and that a new tailored resume replaces the earlier one for that application. The versioning caveat (updatedAt before requestedAt is the older version) and the daily-limit failure mode are exactly the kind of operational context annotations cannot carry. It stops short of describing what happens to in-flight runs or the exact error surface, so not 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-loads the core action and the async return before moving to polling and edge cases, and the paragraphs are organized by concern (do, then observe, then prerequisites, then semantics). It is longer than typical but nearly every sentence carries operational weight; the privacy/usage-tracking sentence is boilerplate rather than tool guidance.

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?

Covers purpose, prerequisites, async lifecycle, how to verify success, how to distinguish stale artifacts, what a replacement does to prior output, and the downstream applyToJob relationship. With an output schema present and the return shape restated inline, an agent has everything needed to invoke and follow up 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 description coverage is 100%, so the baseline is 3, and the nested tailoring object already documents strength, pageLimit and bulletsPerRole in detail. The description adds the meaningful scoping rule that tailoring applies to the resume only and that resume content is constrained to facts already on the candidate's Clera resume, which is not captured by the schema.

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 artifact (write a cover letter and/or resume), the scope (one tracked application, derived from its job description), and the side effect (attach PDFs). An agent can distinguish this generation tool from retrieval siblings like getTailoredResume or listApplications without opening schemas.

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 prerequisites (the application needs a job description; add one with updateApplication first), explicit follow-up routing (getTailoredResume by applicationId, or listApplications for resumeUrl/coverLetterUrl), and a failure/timeout rule (nothing newer after three minutes means it likely hit the daily per-kind limit). The only soft spot is that the overlap with the sibling generateCoverLetter is not addressed, but the when/how guidance is otherwise complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources