Skip to main content
Glama

render_pdf

Render a web page to PDF, PNG, JPEG, WebP or Markdown. Returns the download URL of the finished file; fetch it with your API key as the Bearer token. One tool call: the answer carries the finished file's download URL; no job polling.

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": {
      "url": "<url>"
    },
    "name": "render_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAbsolute http(s) URL of the page to render
formatNoOutput format, defaults to pdf
blockAdsNoFilter ad and tracker requests with community filter lists and hide leftover ad slots. Defaults to false; cosmetic hiding applies to pdf, png, jpeg and webp
fullPageNoCapture the full scrollable page. Defaults to true; set false for a viewport-only capture. Applies to png, jpeg and webp
viewportNoLayout viewport in pixels before capture, 200 to 7680 each. Applies to png, jpeg and webp
landscapeNoLandscape orientation, defaults to false
colorSchemeNoRender the page as if the visitor prefers light or dark mode; site keeps the page's own choice. Defaults to light

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / blockAds
      Added value: +{
      +  "description": "Filter ad and tracker requests with community filter lists and hide leftover ad slots. Defaults to false; cosmetic hiding applies to pdf, png, jpeg and webp",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (not read-only, not idempotent, open-world, non-destructive), and the description usefully adds the return contract: a download URL retrieved with an API-key Bearer token and no job polling. This is real context beyond annotations, though it does not mention URL expiry or failure modes.

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

Conciseness3/5

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

Front-loaded and reasonably short, but the second and third sentences repeat the same fact twice — the answer carries the finished file's download URL and no polling is needed. That duplication dilutes rather than reinforces the message.

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?

There is no output schema, so the description must explain the return value, and it does: a download URL plus how to authenticate the fetch. For a 7-parameter rendering tool this is nearly complete, with only minor gaps around URL lifetime and error behavior.

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 the schema already carries defaults, enum semantics and viewport constraints; the baseline is 3. The description adds no parameter-level detail beyond naming the output formats, which the schema already enumerates.

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 (render) and resource (web page) plus the full set of output formats (PDF, PNG, JPEG, WebP, Markdown), which immediately distinguishes it from the sibling get_pricing/get_usage tools. An agent knows exactly what the tool produces without opening the 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?

Explains the operational flow clearly: one call, no job polling, then fetch the returned URL with the API key as a Bearer token. There are no alternatives or exclusions named, but the sibling tools are unrelated billing/usage endpoints, so no alternative routing is genuinely needed.

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.

Resources