Skip to main content
Glama
Sign In

Import.io

by io.import.mcp
OverviewDiscussionsAdmin

Screen Capture Action

importio_action_screen_capture
Read-onlyIdempotent

Capture a screenshot of the current viewport for debugging or visual evidence inside an importio_play_action pipeline; fields carries the upstream ScreenCaptureAction configuration.

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

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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that capture is limited to the current viewport and that it runs within a play_action envelope, but says nothing about how the image is delivered, its format, or side effects.

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?

A single front-loaded sentence with the action verb first and the pipeline context trailing. No filler, though the semicolon-joined clause about 'fields' reads as boilerplate rather than action-specific detail.

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?

There is no output schema, so the description should cover what the capture returns (image payload vs. reference) but does not. For a 3-parameter tool with a nested object, the definition is adequate on purpose and safety but leaves the deliverable and the content of 'fields' underspecified.

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 coverage is 100%, so the baseline is 3. The description only adds that 'fields' carries the upstream ScreenCaptureAction configuration, without stating which fields matter for a screen capture (format, full-page, selector, etc.), so it adds little beyond the schema's generic envelope 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: 'Capture a screenshot of the current viewport', scoped to 'inside an importio_play_action pipeline'. The scope distinguishes it from generic render/viewport siblings, though it does not name an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a use context ('for debugging or visual evidence') inside play_action pipelines, which implies when to reach for it. However, there is no when-not guidance, no mention of how it relates to sibling viewport/render actions, and no prerequisites.

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