Import.io

Page Text Snippets

importio_page_snippets

Compact helper: optionally navigate to a URL, then return visible text snippets around a query. Use this to inspect neighborhoods around product names, labels, prices, or selector-like words without requesting the full HTML. Supports max_snippets and context_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_snippets / maxSnippets, context_chars / contextChars); provide either form.

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": {
      "query": "<query>"
    },
    "name": "importio_page_snippets"
  }
}

Input Schema

Name	Required	Description
`url`	No	Optional URL to navigate to before searching; omit it to search the current page.
`wait`	No	Wait for the page load to settle before searching.
`query`	Yes	Text to collect visible snippets around.
`maxSnippets`	No	Alias of max_snippets; provide either form.
`proxy_retry`	No	Bounded blocked-page retry policy for the navigation.
`contextChars`	No	Alias of context_chars; provide either form.
`max_snippets`	No	Maximum number of snippets returned.
`context_chars`	No	Characters of surrounding context per snippet.
`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 snippets are collected.

Output Schema

Name	Required	Description	Default
`count`	Yes
`query`	Yes
`snippets`	Yes
`truncated`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed19 schema fields changedNov 9, 2026

addedInput schema / properties / contextChars / description

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

addedInput schema / properties / context_chars / description

Added value: +"Characters of surrounding context per snippet."

addedInput schema / properties / maxSnippets / description

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

addedInput schema / properties / max_snippets / description
```
Added value: +"Maximum number of snippets returned."
```

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 / query / description

Added value: +"Text to collect visible snippets around."

addedInput schema / properties / url / description

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

addedInput schema / properties / wait / description

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

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 snippets are collected."

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false, readOnlyHint=false and destructiveHint=false, so the safety bar is lower. The description still adds real context beyond that: navigation can use managed proxies, blocked pages trigger bounded retries, and it explains why readOnlyHint is false (it may navigate the live page).

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?

Three tight sentences, front-loaded with the core action and then the usage hint and configuration notes. The alias sentence is dense but earns its place given the dual parameter naming scheme.

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?

Eleven parameters with nested objects and an output schema, so return values needn't be explained. The description covers navigation, snippet extraction, proxy/retry behavior and the alias scheme, leaving only minor details (e.g. what happens when no snippets match) unstated.

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 baseline is 3. The description adds only high-level hints (max_snippets, context_chars, proxy selection, bounded retries) plus the snake_case/camelCase alias equivalence, all of which the schema already documents parameter-by-parameter.

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?

States a specific verb and resource: optionally navigate to a URL, then return visible text snippets around a query. It distinguishes itself from full-HTML retrieval ('without requesting the full HTML'), implicitly separating it from importio_get_html/importio_page_text, though it never names those siblings explicitly.

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?

'Use this to inspect neighborhoods around product names, labels, prices, or selector-like words without requesting the full HTML' gives a clear use case and an implicit exclusion (use full-page retrieval when you need everything). It stops short of naming an alternative tool or stating when not to use it.

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?