Skip to main content
Glama
Sign In
svipall

svipall

by ilien-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

browser_do

Run browser actions inside an existing browser_open session: click, type, scroll, wait, verify, navigate, and read pages using refs or selectors.

Instructions

Navigate and act inside a session from browser_open: the same actions as web_act, ref from web_snapshot accepted. Omit url to keep acting on the current page. Returns per-action results and the page content, filtered by query when given.

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": {
      "session_id": "<session_id>"
    },
    "name": "browser_do"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoNavigate here first. Omit to keep acting on the current page.
queryNoKeep only the blocks relevant to these words (BM25).
actionsNoSteps, in order, as in web_act; omit to only read the page.
timeoutNoTimeout in ms for the whole call. Default 90000.
extractionNomarkdown (default), text, or html for the page returned.
session_idYesThe `session_id` browser_open returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates external state. The description adds that actions are performed in order and returns per-action results and page content, which is useful, but doesn't elaborate on destructive potential, required auth, or error behavior beyond the annotations.

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?

Three sentences, front-loaded with purpose and key constraints, no filler. Every sentence earns its place by adding usage context or return info.

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?

Covers core usage, return values, and query filtering, and references sibling tools for session and snapshot. Missing details on error handling or action failure behavior, but adequate given rich schema and annotations.

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 schema already documents all parameters thoroughly, including nested action properties. The description adds marginal value by restating 'omit url to keep acting' and query filtering, but baseline 3 is appropriate when schema does the heavy lifting.

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 specific verbs (navigate, act) and resource (a browser session from browser_open), and explicitly ties to siblings web_act and web_snapshot. An agent can distinguish it from web_act (session vs new page) without opening schemas.

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 says to omit url to keep acting on the current page and references the session from browser_open, giving clear context. However, it doesn't state when to choose this over web_act or browser_open directly, nor exclusions.

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

Deploy Server

Other Tools