Import.io

Form Input Action

importio_action_input_change

Set a form control's value inside an importio_play_action pipeline; fields carries selector and value. Use it to fill form controls after waiting for a selector. For login/forms, prefer wait_for_selector, input_change for each field, then click or keyboard submit. If this fails with synthetic event errors such as preventDefault or target being undefined, do not retry the same action repeatedly; try keyboard-based input if available, otherwise report that the site's event handlers are incompatible with the current browser action.

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

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

Behavior4/5

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

Annotations already declare non-readonly, open-world, non-idempotent, non-destructive, so the bar is lower, yet the description still adds real behavior: synthetic event failures like preventDefault or undefined target, a no-retry policy, and a keyboard fallback. That is concrete operational guidance not present in any structured field.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose, then workflow, then failure handling, and each sentence carries actionable content. The self-reference to "input_change" (the tool's own short name) is slightly ambiguous against the sibling list and costs a bit of clarity.

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 3-parameter nested-object tool with annotations but no output schema, the description covers purpose, sequencing, and error recovery, which is most of what an agent needs. It does not describe what happens on success or whether the value change triggers form submission side effects.

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 the baseline is 3, but the description materially upgrades the vague schema text for `fields` by naming its actual contents (selector and value). The `input` and `optional` envelope parameters remain undescribed beyond the schema's own 'omit it unless' wording.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Set a form control's value") and situates it in the importio_play_action pipeline, which separates it from click/keyboard/select_change siblings by implication. It does not explicitly contrast with select_change for dropdowns, so differentiation is good but not airtight.

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 an explicit recipe: wait_for_selector first, then input_change per field, then click or keyboard submit, which tells the agent both ordering and prerequisites. It never states when not to use it (e.g., use select_change for <select> elements), leaving that inference to the agent.

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?