Skip to main content
Glama

interact_and_test

Execute multi-step web workflows using actions like click, fill, and navigate. Supports sessions, screenshots, and post-run checks for comprehensive testing.

Instructions

Execute a multi-step interaction workflow. Supports 25 actions: click, force_click, fill, force_fill, type, select, select_option, wait, wait_for, wait_for_text, screenshot, navigate, hover, press_key, check, uncheck, scroll_to, scroll_within, evaluate_js, drag, right_click, go_back, go_forward, upload_file, wait_for_network. Can work on an existing session or create an ephemeral page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoURL to open (creates ephemeral page if no session_id)
stepsYesSteps to execute. Each step has 'action' and action-specific fields.
projectNoProject name (optional). With a project: runs in its shared, authenticated context. Without: runs in an isolated context (no shared cookies/login).
run_checksNoChecks to run after steps complete (visual, accessibility, functionality, seo, performance, geo)
session_idNoExisting session ID (alternative to url)
capture_consoleNoCapture console output/errors emitted during the steps and include them in the result (default: false)
screenshot_afterNoTake a screenshot after all steps complete (default: true)
continue_on_errorNoContinue executing steps even if one fails (default: false)
Behavior3/5

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

Without annotations, the description carries full burden. It discloses key behaviors: ephemeral page vs existing session, optional console capture, default screenshot after steps, continue_on_error flag. However, it lacks details on destructive side effects, authentication needs, 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.

Conciseness4/5

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

The description is two sentences, front-loading the purpose and listing actions efficiently. It is concise but could be slightly more structured with examples or sub-bullets for clarity.

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?

Given the tool's complexity (8 params, 25 actions, nested steps), the description covers the basics but lacks details on return values, error handling, and example workflows. It is adequate but leaves several questions unanswered.

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 baseline is 3. The description adds some context beyond schema (e.g., session handling, defaults for screenshot_after and continue_on_error), but does not elaborate on parameter details already present in schema.

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?

The description clearly states the tool's purpose: 'Execute a multi-step interaction workflow.' It lists 25 supported actions and explains session handling, distinguishing it from single-action sibling tools like click_element.

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?

The description implies usage for complex sequences but does not explicitly state when to use this tool vs alternatives like auto_fill_form or individual action tools. No direct guidance on when-not-to-use or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/segentic-lab/periscope-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server