Skip to main content
Glama
Sign In

Import.io

by io.import.mcp
OverviewDiscussionsAdmin

Wait For Loading Action

importio_action_wait_loading
Read-onlyIdempotent

Block until the current page load settles before continuing an importio_play_action pipeline; fields carries the upstream WaitLoadingAction configuration. Use it after navigation on slow sites that must finish loading before content is read; for a specific element's readiness use importio_action_wait_for_selector.

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

Input Schema

NameRequiredDescriptionDefault
inputNoOptional second playAction argument forwarded after the envelope; omit it unless the upstream action expects one.
fieldsYesAction-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.
optionalNoFlag forwarded into the action envelope; omit it unless the upstream action documents it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that the call blocks until load settles, which is useful, but says nothing about timeout behavior, maximum block duration, or what is returned when the page never settles—important for a blocking operation. Deferring configuration to the 'upstream WaitLoadingAction' contract is only partially helpful.

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, zero padding, with the blocking behavior and the pipeline context front-loaded before the routing hint. Every clause carries information an agent needs.

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 blocking, no-output, fully annotated action tool this is nearly complete: purpose, usage context, sibling alternative and the meaning of the required payload are all present. The only real gap is what happens on timeout or a page that never settles, which matters for a blocking call.

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%, so the three parameters are documented at the schema level and the baseline is 3. The description only says 'fields carries the upstream WaitLoadingAction configuration', giving no concrete keys or format, so it adds essentially nothing 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?

States a specific verb and object ('Block until the current page load settles') scoped to a pipeline continuation, and explicitly contrasts the page-load variant with element readiness via importio_action_wait_for_selector. An agent can distinguish this from the sibling wait-for-selector tool 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 concrete usage context ('after navigation on slow sites that must finish loading before content is read') and names the alternative for element readiness. It does not mention when to prefer a plain fixed wait (importio_action_wait) or a region-mutation wait, but the primary routing decision is covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Import.io toolsInspect
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