Skip to main content
Glama

generate_and_save_cv_pdf

Create a customized CV in PDF format by providing your profile and job requirements. The output is saved to a specified directory.

Instructions

Generate tailored CV and save specifically as PDF format (legacy tool - consider using 'generate_cv' which defaults to PDF). If outputPath is not provided, uses DEFAULT_OUTPUT_PATH from environment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marginsNoPDF margins - uses PDF_MARGIN_* env vars if not provided
fileNameNoCustom filename (without extension)
pageSizeNoPDF page size (e.g., 'A4', 'Letter', 'Legal') - uses PDF_PAGE_SIZE env var if not provided
outputPathNoDirectory path where the CV should be saved (optional, uses DEFAULT_OUTPUT_PATH if not provided)
userProfileYes
jobRequirementsYes
Behavior3/5

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

No annotations are provided, so the description must carry the burden. It notes the legacy status and the default output path, but does not disclose other behaviors such as overwrite behavior, return format, or permission requirements.

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 description is concise at two sentences, front-loading the key action and legacy warning. No unnecessary words. It is structured efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has nested parameters and no output schema, but the description does not explain the return value (e.g., file path, success status). With sibling tools, the legacy distinction helps but the description could be more complete regarding tool behavior and output.

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

Parameters3/5

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

Schema description coverage is 67%, so the schema already documents most parameters. The description adds value only for the outputPath parameter (default path). No further parameter semantics are explained beyond 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?

The description clearly states the action: generate a tailored CV and save as PDF. It also identifies itself as a legacy tool and points to an alternative ('generate_cv'), helping distinguish it from siblings.

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?

The description provides explicit guidance by labeling the tool as legacy and recommending 'generate_cv' instead. It also mentions the default behavior for outputPath. However, it does not elaborate on when specifically to use this tool over others.

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/thechandanbhagat/cv-forge'

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