Import.io

Wait Action

importio_action_wait

Read-onlyIdempotent

Pause briefly inside an importio_play_action pipeline; fields carries the upstream WaitAction configuration. For an element's readiness use importio_action_wait_for_selector, for load settling use importio_action_wait_loading, and for a standalone sleep use importio_wait.

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_wait"
  }
}

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.1/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile needs no restating. The description adds the useful fact that this is an envelope forwarder whose behavior is defined by the upstream WaitAction config, but it does not disclose the pause duration semantics, whether fields values are validated, or what happens if the upstream configuration is malformed.

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, front-loaded with the purpose and its execution context, then a compact routing clause. No filler, and the sibling distinctions are packed into a single parallel structure.

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?

For an envelope-style action tool with no output schema and full annotation coverage, the description covers identity, context, and alternative routing. It is incomplete on the one thing an agent still needs: what the forwarded WaitAction configuration should contain and how the pause length is expressed.

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%, so the three parameters are already documented and the baseline is 3. The description's only added meaning is that fields maps to the upstream WaitAction configuration, which is useful but does not say which keys that object accepts.

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?

Specific verb-plus-resource ('Pause briefly') plus the exact scope in which it runs (inside an importio_play_action pipeline), and the fields argument is tied to the upstream WaitAction configuration. An agent can distinguish it from the three other wait siblings 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 names three alternatives and the precise condition that selects each: element readiness -> importio_action_wait_for_selector, load settling -> importio_action_wait_loading, standalone sleep -> importio_wait. The pipeline context implicitly establishes when this tool is the right choice rather than those alternatives.

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?