Import.io

Viewport Action

importio_action_viewport

Idempotent

Resize the browser viewport inside an importio_play_action pipeline; fields carries the width and height in CSS pixels. For standalone viewport setup use importio_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": {
      "fields": "<fields>"
    },
    "name": "importio_action_viewport"
  }
}

Input Schema

Name	Required	Description
`input`	No	Optional second playAction argument forwarded after the envelope; omit it unless the upstream action expects one.
`fields`	Yes	Action-specific configuration forwarded into the action envelope; each tool description states what it should contain where that contract is documented, otherwise it names the upstream configuration fields carries.
`optional`	No	Flag forwarded into the action envelope; omit it unless the upstream action documents it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 9, 2026

addedInput schema / properties / fields / description

Added value: +"Action-specific configuration forwarded into the action envelope; each tool description states what it should contain where that contract is documented, otherwise it names the upstream configuration fields carries."

addedInput schema / properties / input / description

Added value: +"Optional second playAction argument forwarded after the envelope; omit it unless the upstream action expects one."

addedInput schema / properties / optional / description

Added value: +"Flag forwarded into the action envelope; omit it unless the upstream action documents it."

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add context. It adds the pipeline-step framing and the CSS-pixel unit for dimensions, but says nothing about what happens if dimensions are invalid, whether the resize persists across later pipeline steps, or any failure behavior. Useful but thin beyond the annotations.

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 short sentences, front-loaded with the action and scoping context, with the sibling routing statement placed last. No redundant restatement of the name or title.

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 non-destructive, idempotent mutation with an opaque nested `fields` object, no output schema, and annotations covering safety, the description supplies the essential contract (resize, where it applies, what fields holds). Minor gaps remain around persistence and error behavior, but nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the generic envelope descriptions for `fields` and `input` do not convey what actually goes in them. The description fills that gap by stating `fields` carries width and height in CSS pixels, which is real meaning beyond the schema.

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 concrete verb and resource ("Resize the browser viewport") plus its operating context (inside an importio_play_action pipeline), and it explicitly contrasts itself with the sibling importio_viewport for standalone use. An agent can distinguish it from the other 20+ importio_action_* tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states both the when (inside an importio_play_action pipeline) and the when-instead (use importio_viewport for standalone setup), naming the exact alternative tool. That is explicit routing guidance rather than implied usage.

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?