Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
export_resume_pdfA

Export a Markdown resume to PDF.

Resume Markdown format

The resume must use these conventions for the PDF to render correctly:

  • # Full Name — first h1 becomes the page title and name header

  • Unordered list immediately after h1 — becomes an inline contact bar (email, phone, URL, location)

  • Paragraph after the contact list — optional summary/objective

  • ## Section Name — major section headings (Experience, Education, Skills, etc.)

  • ### <span>Job Title, Company</span> <span>Start – End</span> — entry headings; the two <span> tags are required so the title and dates are laid out left/right via flexbox

  • Bullet lists under an entry — achievements and details

When to use file_path vs markdown_content

  • If the user's Markdown file already follows the format above → pass file_path directly.

  • If the file doesn't follow the format (missing <span> tags, wrong structure, etc.) → read the file, rewrite it to match the format, and pass the result as markdown_content.

  • If you are generating a resume from scratch → write the Markdown and pass as markdown_content.

  • If you need a full example of the correct format → read the resume://template resource first.

CSS / styling

By default the built-in stylesheet is applied automatically — no CSS parameter needed. If the user wants to customise the style:

  • Recommended for iterative editing: read resume://style, modify it, save to a local file (e.g. ~/resume.css), then pass css_path pointing to that file. This way the user can tweak the CSS manually between exports without re-sending it, and future exports just reference the same path with no extra tokens.

  • Pass css_content with the raw CSS text — convenient for one-off changes. To see the default stylesheet, read the resume://style resource.

Parameters

  • markdown_content: Raw Markdown text of the resume (mutually exclusive with file_path)

  • file_path: Path to a .md file (mutually exclusive with markdown_content)

  • css_content: Custom CSS text (mutually exclusive with css_path; optional)

  • css_path: Path to a custom CSS file (mutually exclusive with css_content; optional)

  • output_path: Where to write the PDF (default: ~/resume.pdf)

Returns

JSON string: {"pdf_path": "/absolute/path/to/resume.pdf", "success": true}

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
get_resume_templateThe built-in Markdown resume template. Read this resource to understand the exact format conventions required by export_resume_pdf, or to use as a starting point when writing a resume.
get_resume_styleThe built-in default CSS stylesheet applied to all resumes. Read this resource when the user wants to customise the PDF appearance. Modify the CSS and pass the result via the css_content parameter of export_resume_pdf.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ailenshen/resume-markdown-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server