Import.io

Fetch Asset

importio_request_asset

Read-onlyIdempotent

Fetch a single asset (image, stylesheet, script, or XHR response) through the browser engine with its cookies and proxy context; for whole-page content use importio_web_fetch or importio_get_html.

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

Input Schema

Name	Required	Description
`url`	Yes	URL of the asset to fetch.
`timeout`	No	Optional timeout forwarded to the upstream requestAsset call; omit for the engine default.
`resolveCSS`	No	Resolve CSS references before returning the asset.
`replaceExternalReferencesWithS3`	No	Store fetched external references and rewrite the asset to point at the stored copies.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 9, 2026

addedInput schema / properties / replaceExternalReferencesWithS3 / description

Added value: +"Store fetched external references and rewrite the asset to point at the stored copies."

addedInput schema / properties / resolveCSS / description

Added value: +"Resolve CSS references before returning the asset."

addedInput schema / properties / timeout / description

Added value: +"Optional timeout forwarded to the upstream requestAsset call; omit for the engine default."

addedInput schema / properties / url / description
```
Added value: +"URL of the asset to fetch."
```

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description still adds genuine context by disclosing that the fetch runs through the browser engine carrying cookies and proxy configuration — meaning session-authenticated requests behave differently than a plain HTTP client. It does not describe the response shape, but with no output schema that's a modest gap rather than a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the core action front-loaded, a clarifying parenthetical, and the sibling redirect at the end. Every clause earns its place and nothing is repeated from the name or schema.

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 4-parameter, 100%-documented read tool with no output schema, the description covers purpose, scope, credential context, and the alternative tool, which is enough to call it correctly. The only gap is that the returned asset's form (raw bytes vs. rewritten URL when replaceExternalReferencesWithS3 is set) is left unstated and has no output schema to fall back on.

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%, including the non-obvious resolveCSS and replaceExternalReferencesWithS3 flags, so the schema carries parameter meaning completely. The description adds no parameter-level detail (no mention of timeout behavior or what resolving CSS entails), which is the baseline 3 case where structured fields do the work.

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 gives a specific verb and resource ('Fetch a single asset') and immediately enumerates the asset kinds (image, stylesheet, script, XHR response). It also names the differentiator against siblings — asset-level retrieval through the browser engine rather than whole-page content — so an agent can classify it without opening the 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 explicitly routes whole-page use cases to importio_web_fetch and importio_get_html, which is real when-to-use-elsewhere guidance. It stops short of stating exclusions for the asset case itself (e.g., when not to use it at all, or cost/latency tradeoffs), so it's clear but not fully exhaustive.

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?