Import.io

Page Text

importio_page_text

Compact helper: optionally navigate to a URL, then return normalized visible page text from rendered HTML. Use this when raw importio_get_html would be too large or when you need manageable text for inspection. Strips script/style/media content, supports wait_for_selector, and caps output with max_chars. URL navigation supports managed proxy selection and bounded blocked-page retries. snake_case and camelCase parameter names are equivalent aliases (wait_for_selector / waitForSelector, max_chars / maxChars); provide either form.

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_page_text"
  }
}

Input Schema

Name	Required	Description
`url`	No	Optional URL to navigate to before reading; omit it to read the current page.
`wait`	No	Wait for the page load to settle before reading.
`maxChars`	No	Alias of max_chars; provide either form.
`max_chars`	No	Cap on returned text length in characters.
`proxy_retry`	No	Bounded blocked-page retry policy for the navigation.
`proxy_selection`	No	Managed proxy selection for the navigation; omit it to use the server default.
`waitForSelector`	No	Alias of wait_for_selector; provide either form.
`wait_for_selector`	No	CSS selector that must exist before the page is read.

Output Schema

Name	Required	Description	Default
`text`	Yes
`truncated`	Yes
`char_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedNov 9, 2026

addedInput schema / properties / maxChars / description

Added value: +"Alias of max_chars; provide either form."

addedInput schema / properties / max_chars / description

Added value: +"Cap on returned text length in characters."

addedInput schema / properties / proxy_retry / description

Added value: +"Bounded blocked-page retry policy for the navigation."

addedInput schema / properties / proxy_retry / properties / allowResidential

Added value: +{
+  "description": "Alias of allow_residential; provide either form.",
+  "type": "boolean"
+}

addedInput schema / properties / proxy_retry / properties / allow_residential / description

Added value: +"Allow escalation to residential proxies when cheaper pools keep failing."

addedInput schema / properties / proxy_retry / properties / enabled / description
```
Added value: +"Enable bounded navigation retries with fresh proxy checkouts."
```

addedInput schema / properties / proxy_retry / properties / inferCountry

Added value: +{
+  "description": "Alias of infer_country; provide either form.",
+  "type": "boolean"
+}

addedInput schema / properties / proxy_retry / properties / infer_country / description

Added value: +"Infer the proxy country from the URL when proxy_selection.country is not set."

addedInput schema / properties / proxy_retry / properties / maxAttempts

Added value: +{
+  "description": "Alias of max_attempts; provide either form.",
+  "maximum": 3,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / proxy_retry / properties / max_attempts / description
```
Added value: +"Maximum navigation attempts including the first (1 to 3)."
```

addedInput schema / properties / proxy_selection / description

Added value: +"Managed proxy selection for the navigation; omit it to use the server default."

addedInput schema / properties / proxy_selection / properties / type / description
```
Added value: +"Proxy pool to use."
```

addedInput schema / properties / url / description

Added value: +"Optional URL to navigate to before reading; omit it to read the current page."

addedInput schema / properties / wait / description

Added value: +"Wait for the page load to settle before reading."

addedInput schema / properties / waitForSelector / description

Added value: +"Alias of wait_for_selector; provide either form."

addedInput schema / properties / wait_for_selector / description

Added value: +"CSS selector that must exist before the page is read."

First observedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Beyond the annotations it discloses real behavior: script/style/media content is stripped, output is capped by max_chars, navigation supports managed proxy selection with bounded blocked-page retries, and selector waiting is supported. It also explains why readOnlyHint=false is plausible (optional navigation mutates page state). It does not cover return shape or failure modes, but the output schema covers returns.

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?

It is front-loaded with the one-line purpose, then layers usage, behavior, and alias notes in compact sentences. Slightly list-like in the middle (strips..., supports..., caps...), but every sentence carries information an agent would otherwise have to infer.

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 8 parameters, nested proxy objects, an output schema, and annotations already present, the description covers the meaningful gaps: navigation behavior, proxy/retry semantics, text normalization, and the dual naming convention. Only minor omissions remain, such as how max_chars interacts with truncation signaling, which the output schema likely handles.

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 every parameter including the nested proxy objects is already documented in the schema; the baseline is 3. The description reinforces the alias policy (snake_case vs camelCase) and names wait_for_selector and max_chars, but adds no semantics beyond what the schema fields already state.

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?

"Optionally navigate to a URL, then return normalized visible page text from rendered HTML" gives a specific verb plus resource, and the description explicitly positions it against importio_get_html. An agent can distinguish it from the sibling get_html tool without opening either 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?

It states a concrete selection rule: use this when raw importio_get_html would be too large or when manageable text is needed for inspection. That is clear positive guidance, but it does not address other plausible siblings such as importio_page_snippets, importio_extract_data, or importio_web_fetch, so there are no explicit exclusions.

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?