Import.io

Get Rendered HTML

importio_get_html

Read-onlyIdempotent

Return the current rendered page HTML. Use this to discover selectors, inspect unknown data pages, or inspect forms after navigation; the result can be very large, especially when options.replaceAssets is omitted because the websocket engine may inline assets by default. For selector discovery, pass options.replaceAssets=false when you do not need a portable SingleFile capture. For unknown data pages, the discovery pass is importio_web_fetch with wait_for_selector (when known) followed by importio_get_html with options.replaceAssets=false; parse or inspect the HTML instead of guessing extractor/code/function actions. For login/forms, a reliable sequence is importio_get_html, importio_action_wait_for_selector, importio_action_input_change, then importio_action_click or importio_action_keyboard.

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

Input Schema

Name	Required	Description	Default
`options`	No	SingleFile capture options; notably set replaceAssets=false to skip asset inlining when you only need to inspect markup.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / options / description

Added value: +"SingleFile capture options; notably set replaceAssets=false to skip asset inlining when you only need to inspect markup."

First observedNov 9, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's job is to add operational context — and it does: the result can be very large, and the websocket engine may inline assets by default when options.replaceAssets is omitted. That default-behavior disclosure is exactly the kind of trait annotations cannot express.

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?

Front-loaded with the core behavior, then organized by use case. It is dense and somewhat run-on in the middle sentence about replaceAssets, but nearly every clause carries actionable routing or default-behavior information rather than filler.

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

Completeness5/5

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

No output schema exists, and the description compensates by stating what is returned (rendered HTML) and its size characteristics. Combined with the workflow guidance and the single optional parameter's effect, an agent has everything needed to call this correctly and interpret the result.

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 coverage is 100% and the options object is already documented, so the baseline is 3. The description goes further by explaining the practical consequence of replaceAssets (skipping asset inlining when you only need markup, versus a portable SingleFile capture), which adds meaning beyond the schema text.

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 and resource: 'Return the current rendered page HTML.' The word 'rendered' distinguishes it from static-fetch siblings like importio_web_fetch, and the surrounding sentences make clear it is the inspection tool rather than an extraction tool like importio_extract_data or importio_page_text.

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

Usage Guidelines5/5

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

Gives explicit when-to-use cases (selector discovery, unknown data pages, forms after navigation) and names alternatives with conditions: use importio_web_fetch with wait_for_selector for discovery passes, and follow with this tool using replaceAssets=false. It even prescribes an ordered sequence of sibling calls for login/forms, which is unusually actionable.

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

All Import.io 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.

Resources

Need Help?