Import.io

Dispatch Raw Action

importio_play_action

Destructive

Advanced escape hatch: dispatch a raw Import.io Web Scraper action envelope through playAction. The named importio_action_* tools fill in constructorName for you; this tool is for cases where you already know the upstream action JSON shape.

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": {
      "action": "<action>"
    },
    "name": "importio_play_action"
  }
}

Input Schema

Name	Required	Description	Default
`input`	No	Optional second playAction argument forwarded after the envelope.
`action`	Yes	Raw action envelope with constructorName and its configuration; the named importio_action_* tools build this envelope for you.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

addedInput schema / properties / action / description

Added value: +"Raw action envelope with constructorName and its configuration; the named importio_action_* tools build this envelope for you."

addedInput schema / properties / input / description

Added value: +"Optional second playAction argument forwarded after the envelope."

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false and idempotentHint=false, so the risk profile is fully carried by structured fields. The description reinforces this with the framing 'advanced escape hatch' but adds no concrete behavior beyond that – no mention of validation, what happens on a malformed envelope, or whether the action runs immediately in a live session. The extra framing is useful, but for a destructive raw-dispatch tool more specificity would earn a higher score.

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 sentences, no waste, and the critical framing ('escape hatch') is front-loaded before the sibling comparison. Every clause carries information.

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?

Given a 2-parameter tool whose schema fully documents both params and whose annotations fully declare the risk profile, the description covers selection and framing well. The one gap is that no output schema exists, so return behavior of playAction is never described, though that is a minor omission for an advanced escape hatch.

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% and both parameters (action, input) are documented there, including the envelope's constructorName requirement and the 'forwarded after the envelope' role of input. The description adds nothing beyond the schema on parameters, so the baseline 3 applies – it refers generically to 'the upstream action JSON shape' without new syntax guidance.

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 (dispatch) and resource (raw Import.io Web Scraper action envelope via playAction), and explicitly contrasts itself with the named importio_action_* tools that pre-fill constructorName. An agent can distinguish this escape hatch from the 22 sibling 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?

Names both the alternative (the importio_action_* tools) and the selecting condition (you already know the upstream action JSON shape). The when-to-use and when-not-to-use cases are both stated, leaving nothing to inference.

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?