Skip to main content
Glama
yinnho

AginxBrowser

by yinnho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust

render_pdf

Convert any URL into a multipage PDF, PPTX, DOCX, or PNG deck. Print mode paginates at block boundaries; slides mode creates one page per CSS-selected element.

Instructions

Cut a rendered page into pages and package as PDF, PNGs, PPTX or DOCX. Print mode (no selector) paginates the document into fixed-height pages (default 794x1123, A4 @96dpi), breaking at top-level block boundaries — no half-cut text where a break can land on a block edge. Slides mode (selector set) makes one page per match, sized to that element — generate an HTML deck with one .slide per page and each becomes a deck page. format "pdf" (default) returns base64 image-based PDF; "png" returns one base64 PNG per page in pages_base64; "pptx" returns a base64 PPTX (one slide per page, deck-sized to the largest page); "docx" returns a base64 DOCX (one page-sized section per page, each section keeps its own height). Returns page count and packaging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPage URL to cut into pages.
widthNoPage width in CSS pixels. Default 794 (A4 @96dpi).
formatNoOutput format: "pdf" (default), "png" (one base64 PNG per page), "pptx" (one slide per page, image-based), "pptx-native" (editable: element-level DrawingML — real text runs, gradient shapes, image parts; requires `selector`), or "docx" (one page-sized section per page).pdf
heightNoPage height in CSS pixels — print pagination only. Default 1123.
selectorNoCSS selector; present → slides mode (one page per match, sized to the element). Absent → print mode (fixed-height pages at block boundaries).
max_pagesNoSafety cap on emitted pages. Default 50.
use_proxyNoRoute through proxy (for blocked foreign sites)
jpeg_qualityNoJPEG quality for PDF page embedding (1-100). Default 90.
tls_fingerprintNoTLS fingerprint override (stealth mode only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

With only a title annotation and no read-only/destructive hints, the description carries the behavioral burden. It discloses pagination boundaries, slide-per-match behavior, image-based PDFs, per-format packaging details, and the return of page count. It stops short of describing side effects like network fetching or permission requirements, but these are largely non-mutating.

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 dense but well-structured: purpose first, then mode behavior, then format-specific output details, then return summary. Every clause adds information, though the long middle sentence packs many behaviors together and could be slightly hard to scan.

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?

For a tool with 9 parameters, two modes, and five output formats, the description covers the essential decisions and return characteristics. With no output schema, it supplies high-level return information ('page count and packaging') and names pages_base64 for PNGs, but does not fully specify the response envelope.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by explaining mode-dependent behavior (block-boundary breaks vs element-sized pages), the deck-size behavior of PPTX, and the section-height behavior of DOCX. This is more than a restatement of parameter names.

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 uses a specific verb ('cut') and resource ('rendered page') and enumerates the exact output formats (PDF, PNGs, PPTX, DOCX). It clearly distinguishes itself from sibling rendering tools like render_video and render_markdown by describing page-based packaging.

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 gives clear when-to-use guidance for the two modes: print mode when no selector is set, and slides mode when a selector is provided. It does not explicitly contrast the tool with sibling alternatives, but the mode-level guidance is strong and actionable.

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

Deploy Server

Other Tools