Skip to main content
Glama

Convert to PDF

convert_to_pdf

Make a PDF from Word, Excel or PowerPoint files, images (one page each, in order), an EPUB, or a public web page (url). For content you write yourself, use create_pdf.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "convert_to_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoA public web page to render as a PDF.
filesNoFiles the person attached in ChatGPT, in order (filled in by ChatGPT).
file_idsNoFynePDF file_ids, in order.
file_urlsNoPublic links to the files, in order.
page_layoutNoFor url.
library_file_idNoA file from the person's FynePDF Library (from list_library_files).

Output Schema

NameRequiredDescriptionDefault
cardNo
filesYes
stepsYes
job_idYes
statusYes
creditsYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedOutput schema / properties / files / items / properties / bytes / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / bytes / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / files / items / properties / download_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / download_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / files / items / properties / pages / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / files / items / properties / pages / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / bytes_after / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / bytes_after / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / bytes_before / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / bytes_before / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / pages_after / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / pages_after / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / steps / items / properties / pages_before / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / steps / items / properties / pages_before / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and non-idempotent, and the description adds genuine behavior: images become one page each, in the given order. It omits anything about the async job model implied by the get_job sibling, the 20-item cap, or what happens when multiple input channels are supplied at once — meaningful gaps for a conversion operation.

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?

Two sentences, no filler, with the accepted inputs front-loaded and the sibling routing as the closing clause. Every phrase carries information.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and the accepted input types are fully enumerated. What is missing is confirmation of async/job behavior for a potentially long conversion — a moderate gap given 6 optional parameters and no required inputs.

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 100%, so baseline is 3. The description adds the image-to-page mapping and confirms 'url' selects the page_layout path, but it never explains the distinction between the four competing input channels (files, file_ids, file_urls, library_file_id), which is the main semantic ambiguity an agent faces here.

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?

States a specific verb-plus-resource ('Make a PDF') and enumerates the exact accepted source types: Office files, images, EPUB, public web page. It explicitly separates itself from the sibling create_pdf, so an agent can choose between the two without opening a schema.

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 one real routing decision an agent faces — converting existing content vs. authoring new content — is handled explicitly ('For content you write yourself, use create_pdf'). It does not cover the reverse-direction sibling convert_from_pdf or when to pick among the four file-input channels, but the primary when-to-use signal is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.