Import.io

Set Viewport Size

importio_viewport

Idempotent

Set the browser viewport size in CSS pixels for subsequent steps; to resize inside an importio_play_action pipeline use importio_action_viewport.

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": {
      "width": "<width>",
      "height": "<height>"
    },
    "name": "importio_viewport"
  }
}

Input Schema

Name	Required	Description	Default
`width`	Yes	Viewport width in CSS pixels.
`height`	Yes	Viewport height in CSS pixels.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026
- addedInput schema / properties / height / description
```
Added value: +"Viewport height in CSS pixels."
```
- addedInput schema / properties / width / description
```
Added value: +"Viewport width in CSS pixels."
```
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 readOnly=false, idempotent=true, destructive=false, openWorld=false, so the safety profile is covered structurally. The description adds meaningful scope context with "for subsequent steps," telling the agent the change persists across later calls. It does not say whether an active browser/page is required, whether the size resets between sessions, or how device scale factor is treated.

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, front-loaded with the action and unit, followed immediately by the disambiguation clause. Nothing is redundant or padded.

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 two-required-param setter with full schema coverage, no output schema, and annotations covering the safety profile, this is nearly sufficient. The only real gap is the lack of any precondition about an active page or session.

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 properties already document "in CSS pixels," so the description adds no parameter meaning beyond the structured schema. With two well-documented params, the 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?

States a specific verb and resource ("Set the browser viewport size") with the unit (CSS pixels), and explicitly distinguishes itself from the sibling importio_action_viewport. An agent can tell which of the two viewport tools to pick 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?

Gives a clear routing rule: use this one for standalone/session-level steps and importio_action_viewport when inside an importio_play_action pipeline. It does not state prerequisites (e.g., a page must already be open) or typical/default dimensions, so usage context is clear but not 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?