Import.io

Flow Control Action

importio_action_flow_control

Branch or halt an importio_play_action pipeline through the upstream FlowControlAction; fields carries its configuration. Use it only when you know the upstream flow-control shape; simple repetition belongs in importio_action_loop.

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

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

A3.6/5.0

Behavior3/5

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

Annotations declare the tool is not read-only, not idempotent, and not destructive, so the safety profile is already covered. The description adds the genuinely useful behavioral trait that this alters pipeline control flow rather than page state, but it omits what halting does to the run's result and whether branching can skip or repeat steps.

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?

Two tight sentences with the primary effect front-loaded and the exclusion second; nothing is padding. The phrase 'through the upstream FlowControlAction' is slightly jargon-heavy but carries real information.

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 opaque passthrough wrapper with a nested free-form object and no output schema, the description tells the agent it needs external knowledge of the upstream action without pointing anywhere to get it. It is adequate to prevent misuse but leaves the actual contract for 'fields' and the effect of halting unexplained.

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 baseline is 3. The description's note that 'fields carries its configuration' largely repeats the schema's own wording about action-specific configuration being forwarded into the envelope, and it gives no concrete field names or shape for this action.

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 pair and effect ('Branch or halt an importio_play_action pipeline') plus the mechanism ('upstream FlowControlAction'), which is far more informative than the title alone. It is distinguishable from data-extraction or navigation siblings, though it never explains what a 'branch' actually selects.

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?

Explicitly routes repetition cases to a named alternative (importio_action_loop) and adds a precondition ('only when you know the upstream flow-control shape'). The precondition is soft and does not say where an agent would learn that shape, so it is not a full when/when-not contract.

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?