Import.io

Scroll To Position (Deprecated)

importio_scroll_to

Deprecated: direct engine scrollTo(top, left) kept for compatibility; use importio_action_scroll for new work. Coordinates are pixel offsets from the page's top-left corner.

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": {
      "top": "<top>",
      "left": "<left>"
    },
    "name": "importio_scroll_to"
  }
}

Input Schema

Name	Required	Description	Default
`top`	Yes	Pixel offset from the top edge of the page.
`left`	Yes	Pixel offset from the left edge of the page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026
- addedInput schema / properties / left / description
```
Added value: +"Pixel offset from the left edge of the page."
```
- addedInput schema / properties / top / description
```
Added value: +"Pixel offset from the top edge of the page."
```
First observedNov 9, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true. The description adds that this invokes the engine's raw scrollTo rather than a higher-level action, which is useful context, but it does not say whether the call waits for the scroll to settle or how failures surface. With annotations carrying the safety profile, this is adequate but thin.

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?

Two compact sentences with the deprecation notice front-loaded and the alternative named before any parameter detail. No sentence is wasted.

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 deprecated two-parameter tool with full schema coverage and no output schema, the description supplies the essential facts: status, replacement, and coordinate frame. Only post-call behavior such as scroll completion semantics is unaddressed, a minor gap given the tool's deprecation.

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 coverage is 100% and both parameters already document their pixel-offset meaning from the respective edges. The description's 'pixel offsets from the page's top-left corner' merely reframes what the schema states, adding no format, range, or unit nuance beyond it. Baseline 3 applies.

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 names a specific operation (direct engine scrollTo with top/left pixel offsets) and identifies its replacement sibling, importio_action_scroll. An agent can distinguish it from the higher-level scroll action 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 explicitly routes new work to importio_action_scroll and frames this tool as compatibility-only, which is clear guidance. It does not state what the remaining legitimate uses of the deprecated path are, so the exclusion side is only partially covered.

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?