Rendex: Rendering API for Images, PDFs & Content Extraction

Extract Reader-Mode Content

rendex_extract

Read-only

Use this when the user asks to read, extract, get the text/content/article of, or summarize a webpage/URL. Extracts clean reader-mode content from any webpage as Markdown, JSON, or HTML. Runs a full Chromium render pass, so it captures content after JavaScript runs, including single-page apps (SPAs). Strips nav, ads, and boilerplate, returning the article body plus title, byline, and excerpt. Great for feeding page content to an LLM, summarization, or RAG ingestion. Costs 1 render credit per call.

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": "rendex_extract"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	The webpage URL to extract readable content from (a schemeless host like 'example.com' is accepted).
`device`	No	Device preset that sets viewport, scale factor, and user agent in one shot. E.g. 'iphone_15' to extract the mobile version of a page.
`timeout`	No	Maximum seconds to wait for page load (5-60). Cloudflare has a 60s hard cap.
`blockAds`	No	Block ads and trackers before extraction
`waitUntil`	No	Page readiness event. networkidle2 (default) is best for most sites. Use domcontentloaded for speed, networkidle0 for completeness.	networkidle2
`extractFormat`	No	Output shape — markdown (default, LLM-friendly prose), json (structured fields: title/byline/excerpt/siteName/length), or html (cleaned reader-mode HTML).	markdown
`hideSelectors`	No	CSS selectors to hide (display:none) before extraction. E.g. ['.modal', '#newsletter-popup'] to remove overlays. Max 50 selectors.
`blockCookieBanners`	No	Hide common cookie/consent walls (GDPR/CCPA banners) before extraction. A curated selector list, lighter than custom hideSelectors.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJun 27, 2026

changedInput schema / properties / url / description

Previous value: -"The webpage URL to extract readable content from."New value: +"The webpage URL to extract readable content from (a schemeless host like 'example.com' is accepted)."

AddedMay 28, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the annotations (readOnly, openWorld, non-idempotent, non-destructive), the description discloses the full Chromium render pass, JavaScript/SPA support, boilerplate stripping, the returned fields (title, byline, excerpt), and an explicit cost of 1 render credit per call. The credit cost is operationally important information that appears nowhere in the structured fields.

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?

Sentences are ordered well: trigger condition first, mechanism next, output shape, then cost. There is minor redundancy—'summarize' appears in the trigger list and again in 'Great for feeding page content to an LLM, summarization, or RAG ingestion'—but the description remains tight for a tool with this much behavior to convey.

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?

With eight parameters, full schema coverage, and no output schema, the description supplies what is missing: JS rendering behavior, boilerplate removal, output formats, and per-call billing cost. It never addresses failure modes (paywalls, bot-blocked pages, timeouts) that matter for an open-world fetch tool, which is the one substantive gap.

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% and each parameter already carries a detailed description with defaults, enums, and ranges, so the schema does the heavy lifting. The description adds only light corroboration of extractFormat's three shapes and the general 'any webpage' scope, with no new syntax or constraint meaning beyond the schema.

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

Purpose4/5

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

The description names a specific verb ('extract') and resource ('clean reader-mode content from any webpage') plus the output shapes (Markdown, JSON, HTML), which is far more precise than the title alone. It does not explicitly distinguish itself from siblings like rendex_render_link or rendex_screenshot, so an agent must infer the boundary rather than read it.

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 opening sentence gives a concrete trigger list ('read, extract, get the text/content/article of, or summarize a webpage/URL'), so an agent knows exactly what user intent selects this tool. It stops short of the top mark because no exclusion conditions or named alternatives are given (e.g., 'use rendex_screenshot instead when the user wants a visual').

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

All Rendex: Rendering API for Images, PDFs & Content Extraction tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.