Skip to main content
Glama

FileToPDF

by dev.filetopdf

Convert a file (by URL) to PDF

convert_file

Convert a file fetched from a public URL into a PDF. Auto-detects the engine from the extension: Office docs (DOCX, XLSX, PPTX, ODT, RTF, TXT, CSV…), images (PNG, JPG, WebP…), HTML, Markdown, or an existing PDF (passthrough). Costs 1 credit on success. Returns the PDF as an embedded resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the file to download and convert.
pdfaNoPDF/A conformance level, e.g. "PDF/A-2b". (Pro/Scale/trial only.)
pdfuaNoProduce an accessible PDF/UA document.
passwordNoPassword to open a protected source document.
landscapeNoRender in landscape orientation. (Pro/Scale/trial only.)
save_pathNoOptional absolute path to also write the PDF to on disk.
userPasswordNoPassword required to open the resulting PDF.
ownerPasswordNoOwner password controlling permissions on the resulting PDF.
nativePageRangesNoPage ranges to include, e.g. "1-3".

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses important behavioral details beyond annotations: it costs 1 credit, returns an embedded resource, and auto-detects engine. With only openWorldHint annotation, this adds significant transparency, though it could mention error scenarios or size limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loading the core action, then efficiently listing supported types and cost. No redundant information.

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?

Given 9 parameters and no output schema, the description covers the main function and return format but lacks details on parameter interactions, error handling, or limits. It is adequate but not fully comprehensive.

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 coverage is 100%, so baseline is 3. The description does not add meaningful semantics beyond the schema for individual parameters; it focuses on high-level tool behavior instead of enriching parameter understanding.

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 converts a file from a public URL to PDF, lists supported formats, and mentions auto-detection of the engine. It distinguishes from siblings like convert_html and convert_markdown by covering those plus many more types.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use (for general file conversion to PDF) but does not explicitly state when not to use or compare with sibling tools. It lacks guidance on choosing between convert_file and the more specific convert_html or convert_markdown.

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

All FileToPDF toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a distinct input source: convert_file handles files from URLs, convert_html deals with raw HTML strings, convert_markdown processes Markdown, and get_account manages account info. There is no overlap.

Naming Consistency5/5

All tools follow a clear verb_noun pattern (convert_file, convert_html, convert_markdown, get_account), with consistent verb choice and naming style.

Tool Count5/5

Four tools is well-scoped for the domain: three conversion methods covering common input formats and one account tool. No tool is superfluous or missing.

Completeness4/5

The set covers the main conversion workflows (file URL, HTML, Markdown) and account management. Minor gaps like direct file upload or advanced formatting options for file conversion exist but do not hinder core functionality.

Resources