Import.io

Call Engine Method

importio_call_method

Destructive

Advanced escape hatch: call any allowlisted websocket method by name with positional params; use the dedicated importio_* tool when one exists for the method.

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": {
      "method": "<method>"
    },
    "name": "importio_call_method"
  }
}

Input Schema

Name	Required	Description	Default
`method`	Yes	Method name; allowed: playAction, goto, render, queryQueue, wait, viewport, stop, scrollTo, refresh, getHTML, extractData, suggestData, requestAsset.
`params`	No	Positional arguments forwarded to the method, in order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedInput schema / properties / method / description

Added value: +"Method name; allowed: playAction, goto, render, queryQueue, wait, viewport, stop, scrollTo, refresh, getHTML, extractData, suggestData, requestAsset."

addedInput schema / properties / params / description

Added value: +"Positional arguments forwarded to the method, in order."

First observedNov 9, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotency, so the risk profile is largely supplied by structured data. The description is consistent with those hints but adds no behavioral context beyond them — it never warns that reachable methods like goto, render, or playAction mutate live page/session state, nor how errors surface for a disallowed method name.

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 role ('Advanced escape hatch') front-loaded and the routing rule in the second clause. Every phrase earns its place; nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Parameters and risk hints are fully covered by the schema and annotations, and no output schema exists, so the description should say what an invocation returns (raw method result?) and how invalid or disallowed methods fail. For a destructive escape hatch that forwards arbitrary positional args, that return/error behavior is a meaningful omission.

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%: the schema already enumerates every allowed method name and explains that params are positional arguments forwarded in order. The description merely restates 'by name with positional params,' adding only the word 'allowlisted,' which the schema's enum also conveys. 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 uses a specific verb+resource ('call any allowlisted websocket method by name with positional params') and immediately distinguishes the tool from its siblings by telling the agent to prefer the dedicated importio_* wrapper. 'Advanced escape hatch' frames the tool's role in the surface without ambiguity.

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 gives an explicit when-not: 'use the dedicated importio_* tool when one exists for the method', which is the primary routing decision an agent faces among ~40 siblings. It stops short of stating the positive trigger (only when no dedicated tool covers the method) or warning that the escape hatch bypasses the safety of the wrappers.

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?