Skip to main content
Glama

export_resume_pdf

Export a Markdown resume to a styled PDF. Accepts file path or Markdown content, and optional custom CSS for personalization.

Instructions

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}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdown_contentNo
file_pathNo
css_contentNo
css_pathNo
output_pathNo~/resume.pdf

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but the description fully covers behavior: expected markdown format, output as JSON, file writing via output_path, and CSS customization options. It explains the internal rendering requirements (e.g., <span> tags) and the return structure.

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?

Well-structured with clear sections and bullet points, but slightly verbose. Could be trimmed slightly without losing clarity, but it remains readable and front-loads the core purpose.

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?

Given no annotations and no sibling tools, the description is exhaustive: covers markdown format, parameter usage, CSS customization, output specification, and examples. It leaves no significant gaps for an agent to misuse.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description explains each parameter's purpose, mutual exclusivity (content vs path), defaults, and relationship to tool behavior. Adds substantial meaning beyond the raw 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?

The description clearly states the tool exports a Markdown resume to PDF, specifies the required Markdown format, and differentiates between input methods. It leaves no ambiguity about the tool's function.

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?

Provides explicit guidance on when to use file_path vs markdown_content, how to handle malformed markdown, and how to customize CSS. Includes concrete examples like reading the template for correct format.

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

Install Server

Other Tools

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