Skip to main content
Glama

Generate my resume PDF

generateResumePdf

Renders the candidate's resume draft to a PDF and returns a download link that works for an hour. With saveAsCleraResume true the PDF also becomes the candidate's primary resume, the one Clera sends with introductions, and shows up in listResumes. Pass template to switch the design first. Needs a draft with at least a name.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "generateResumePdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdNoA resume version's draftId from readResumeDraft. Leave it out for the default version.
templateNo
saveAsCleraResumeNoAlso make it the primary resume Clera sends with intros. Default false.

Output Schema

NameRequiredDescriptionDefault
resumeIdYes
expiresAtYes
signedUrlYes
dashboardLinkYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, idempotentHint=false, destructiveHint=false; the description goes further by disclosing the one-hour link expiry, the persistent side effect of promoting the PDF to primary resume, the downstream visibility in listResumes, the design-switch behavior of template, and a data-recording notice. This is exactly the kind of consequence and TTL information annotations cannot carry.

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 core action, return value, and side effect come first, followed by parameter hints and a mandatory-seeming privacy note. It is tight overall, with only slight redundancy where "the one Clera sends with introductions" restates the parameter description, but nothing is wasted in a way that harms comprehension.

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?

An output schema exists, yet the description still front-loads the most important return characteristic (hour-limited download link) and covers prerequisites, defaults, and side effects for a 3-parameter mutation tool. An agent has everything needed to invoke it 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 coverage is 67%, with template carrying only an enum and no inline description; the description partly compensates by explaining that template switches the design before rendering. It also adds consequence-level meaning to saveAsCleraResume beyond the schema's "primary resume Clera sends with intros" wording (visibility in listResumes), though it does not explain how the three template values differ.

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 names a specific verb and resource ("Renders the candidate's resume draft to a PDF") and states what the call yields (a download link valid for an hour). It also clarifies the side effect that distinguishes the saveAsCleraResume path (becomes the primary resume, appears in listResumes), so an agent knows exactly what this tool does versus generateCoverLetter or setPrimaryResume.

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?

It gives the precondition ("Needs a draft with at least a name") and notes the draftId default ("Leave it out for the default version"), plus mentions template should be passed to switch design first. What's missing is any explicit when-not guidance, e.g. when to prefer setPrimaryResume over saveAsCleraResume=true, so it sits at clear-context-no-exclusions.

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