not-boring-resume-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| load_cvA | Return the CV YAML with its embedded photo removed. Read the CV through this tool instead of opening the file directly: the photo is a base64 data URI that is huge and useless for tailoring. Work from the returned text; the photo is reattached automatically by generate_pdf. Args: cv_path: path to the CV YAML. |
| generate_pdfA | Render a YAML CV into a one-page PDF via notboringresume.cloud. Writes the PDF to Args:
yaml: the CV content in YAML (already tailored to the job offer). Omit it to
render the site's built-in default CV (handy for a quick manual test).
output_path: where to save the PDF, e.g. output/Acme/backend-dev/cv.pdf.
Defaults to cv.pdf in the current directory.
cv_path: path to the original CV YAML. When given, the photo from that file is
reattached to |
| generate_letter_pdfA | Render a cover letter written in Markdown into a clean, classic A4 PDF. Provide the letter either inline via Args:
text: the cover letter in Markdown. Blank lines separate paragraphs; a
top-level heading ( |
| fetch_offerA | Fetch a job offer from a URL and return its visible text. Use this when the user gives a link instead of pasting the offer. The page is rendered in a headless browser, so it works on JavaScript-heavy job boards. Args: url: the job offer URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tailor_cv | Tailor the CV to a job offer and render the PDF (no cover letter). Args: offer: the job offer text (plain text or a URL). cv_path: path to the CV YAML, in case it is named differently. |
| tailor_cv_and_letter | Tailor the CV, render the PDF, and write the cover letter. Args: offer: the job offer text (plain text or a URL). cv_path: path to the CV YAML, in case it is named differently. cover_letter_path: path to the cover letter template, in case it differs. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: fetching a job offer, generating a cover letter PDF, generating a CV PDF, and loading CV YAML. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern (fetch_offer, generate_letter_pdf, generate_pdf, load_cv), using snake_case and clear action verbs.
With 4 tools, the server is well-scoped for its purpose (resume/CV generation). Each tool covers a essential step in the workflow without unnecessary extras.
The tool surface covers the key workflow (fetch offer, load CV, generate CV and letter), but lacks explicit editing or versioning tools. Minor gap, but core functionality is present.