Skip to main content
Glama

pdf_render

Renders PDF pages as PNG, JPEG, or WEBP images so you can view, share, or reuse document content in image formats.

Instructions

Renders a PDF. [Input: PDF (.pdf) | Output: PNG/JPEG/WEBP images]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "pdf_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesThe input PDF file path.
formatNoOutput image format: png, jpeg/jpg, webp. Optional, defaults to inferring from output path or png.
outputYesThe output PDF file path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior1/5

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

No annotations exist, so the description carries the full behavioral burden, yet it discloses nothing about page handling (one image per page vs. first page only), output naming for multi-page PDFs, resolution/DPI, overwrite behavior, or file-writing side effects. The only behavioral fact conveyed is the format conversion, which is already implicit in the name and schema.

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?

Two short fragments with no filler, and the input/output contract is front-loaded. It is terse to the point of under-specification, but no sentence is wasted.

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

Completeness2/5

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

For a file-producing conversion tool with zero annotations and no output schema, the definition is too thin: nothing describes how multi-page PDFs map to output files, where images are written, or what happens on failure. The type contract is present but the operational contract is absent.

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's format list (PNG/JPEG/WEBP) mirrors the schema's format enum guide. It does implicitly correct the schema's misleading "output PDF file path" by declaring the output is images, which is a small value-add but not expanded into naming or multi-page semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Renders a PDF" states a verb and resource, and the bracket clarifies the conversion direction (PDF in, raster image out). However, "renders" is ambiguous next to siblings like pdf_extract_images, and the description never distinguishes rasterizing pages from extracting embedded images.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, no prerequisites, and no mention of alternatives such as pdf_extract_images or pdf_convert_html. The agent must infer the use case from the input/output type bracket alone.

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