Import.io

Click Action

importio_action_click

Destructive

Click a confirmed button, link, or checkbox inside an importio_play_action pipeline. Use fields.selector for a confirmed button, link, or checkbox; the server builds Chromium's MouseEvent target. Verify the page changed after the click. For form submission, click the submit button or use importio_action_keyboard for Enter. Hover, drag, and other pointer work a selector click cannot express belongs in importio_action_mouse.

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

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

Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered. The description still adds real behavior beyond them: the server constructs Chromium's MouseEvent target from the selector, and the caller should verify the page changed afterward — an important post-condition for a non-idempotent, destructive action. It stops short of warning about irreversible side effects or auth/permission needs, which keeps it off a 5.

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?

Three sentences, front-loaded with the core action and the required field, followed by usage routing. Every sentence carries information, though the Chromium MouseEvent detail is slightly implementation-flavored and could be trimmed without loss for an agent.

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

Completeness5/5

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

With no output schema, the description covers what an agent needs: the required selector contract, the post-click verification step, and the boundary against keyboard and mouse siblings. Complexity is low and the coverage is proportionate.

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%, but the schema's `fields` object is a generic additionalProperties bag with no action-specific content documented. The description supplies the one thing the schema cannot: that `fields.selector` is what drives the click. It leaves `input` and `optional` to the schema, which already explains them adequately.

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 (click) and resource (confirmed button, link, or checkbox) scoped to an importio_play_action pipeline. It explicitly contrasts with importio_action_keyboard and importio_action_mouse, so an agent can distinguish it from the pointer and key 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?

Gives when-to-use (fields.selector for a confirmed button/link/checkbox), an alternative path for form submission (click the submit button or use importio_action_keyboard with Enter), and an explicit exclusion routing hover/drag/other pointer work to importio_action_mouse. Nothing about tool selection is left 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?