Import.io

Keyboard Action

importio_action_keyboard

Destructive

Type text or send key sequences through real keyboard events inside an importio_play_action pipeline, for sites whose handlers ignore synthetic value changes; fields carries the text or keys to send. For direct value setting use importio_action_input_change, and for a single key press use importio_action_key.

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

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

Behavior3/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 adds useful context about real keyboard events versus synthetic value changes, but never explains what the destructive risk actually is (e.g. typing into a focused field may overwrite or submit), nor focus requirements, key-sequence format, or rate limits.

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?

One sentence establishes purpose, pipeline context and rationale, followed by one sentence that routes to the alternatives. Front-loaded, zero filler, no repetition of the title or annotations.

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 a destructive, non-idempotent, open-world mutation tool with nested object parameters and no output schema, the definition covers purpose, routing and the fields contract adequately. It is silent on what a call can destroy, whether it appends or replaces existing field content, and what it returns, which are material gaps given destructiveHint=true.

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 baseline is 3, but the description genuinely improves on the generic schema text by stating that 'fields carries the text or keys to send' — the schema only says fields is 'action-specific configuration forwarded into the action envelope'. It still does not specify the expected shape of that payload (string vs array of key names), which keeps it below 5.

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 resource ('Type text or send key sequences through real keyboard events') plus the operating context ('inside an importio_play_action pipeline') and the precise problem it solves ('sites whose handlers ignore synthetic value changes'). It explicitly distinguishes itself from importio_action_input_change and importio_action_key, so an agent can choose without opening the schemas.

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 two alternatives with the condition that selects each: importio_action_input_change for direct value setting and importio_action_key for a single key press. The implicit when-to-use is also given (sites that ignore synthetic value changes), 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?