Skip to main content
Glama
Sign In

Import.io

by io.import.mcp
OverviewDiscussionsAdmin

Extract Data Action

importio_action_extract_data
Read-onlyIdempotent

Run structured extraction inside an importio_play_action pipeline; fields carries the extraction runtimeConfig. Use it for structured extraction when you already know the extraction configuration. Do not use it for selector discovery, unknown data pages, or login/forms. Empty results usually mean the config/selectors did not match the rendered page. For a one-off extraction outside a pipeline use importio_extract_data.

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

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

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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds a genuinely useful failure-mode signal beyond the annotations: empty results usually indicate the config/selectors did not match the rendered page. It does not cover result shape or timeout behavior, which keeps it from 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.

Conciseness5/5

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

Four short sentences: purpose and pipeline context first, then the use/don't-use routing, then a failure-mode note. No filler, no repetition of annotation data, and the most decision-relevant information is front-loaded.

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 action with nested objects and no output schema, the description covers purpose, routing, alternatives, and the most likely failure mode. The main residual gap is that the expected structure of `fields` and the shape of successful results are not spelled out.

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 schema explicitly defers the contract ('each tool description states what it should contain'), and the description picks that up by identifying `fields` as the extraction runtimeConfig. It does not describe the runtimeConfig's internal structure, so the compensation is only partial.

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 ('Run structured extraction') plus the exact execution context ('inside an importio_play_action pipeline'), and distinguishes itself from importio_extract_data by name. An agent can separate this from the ~19 other importio_action_* siblings without opening the 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 explicit when-to-use ('when you already know the extraction configuration'), explicit when-not ('selector discovery, unknown data pages, or login/forms'), and names the correct alternative ('For a one-off extraction outside a pipeline use importio_extract_data'). All three routing signals are present.

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