Skip to main content
Glama
Gwakko

agent-in-browser

by Gwakko
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

navigate

Load a URL in a browser tab or perform back, forward, and reload history actions, then wait until the page loads and return the final title, URL, and tab ID.

Instructions

Load a URL in a tab, or go back, forward or reload its history, then wait until the page has loaded (or timeout_ms passes, reported as "still loading"). Returns the final title, URL and tab id. Give either url or action. Loading a URL clears the tab's captured network requests. Element refs from earlier snapshots become invalid, so call snapshot next. Use tab_new to open a page in a new tab and click on links to follow them.

Input Schema

NameRequiredDescriptionDefault
tabNoTab id from tabs_list. Defaults to the current tab.
urlNoDestination URL; scheme defaults to https://, file:// and about: URLs are accepted.
actionNoHistory action to run instead of loading a url.
timeout_msNoHow long to wait for the page to finish loading, in milliseconds (default 30000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • changedInput schema / properties / action / description
      Previous value: -"History action instead of url."New value: +"History action to run instead of loading a url."
    • changedInput schema / properties / timeout_ms / description
      Previous value: -"Load timeout (default 30000)."New value: +"How long to wait for the page to finish loading, in milliseconds (default 30000)."
    • changedInput schema / properties / url / description
      Previous value: -"Destination URL; scheme defaults to https://"New value: +"Destination URL; scheme defaults to https://, file:// and about: URLs are accepted."
  2. First observedv0.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true. The description adds crucial behavioral traits: waiting for page load, timeout handling reported as 'still loading', clearing captured network requests, and invalidating element refs requiring a snapshot next. These are non-obvious side effects that go well beyond annotations.

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 front-loaded with the core action and return values, then adds important caveats about side effects and alternatives. Every sentence earns its place, though it's slightly dense and could be broken into clearer clauses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a navigation tool with no output schema, the description covers return values (title, URL, tab id), timeout behavior, side effects on network requests and element refs, and next steps (snapshot). Nothing essential for correct invocation is missing.

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 schema already documents all parameters. The description adds marginal value by noting 'Give either url or action' and scheme defaults, but most parameter meaning is already in the schema. Baseline 3 is appropriate.

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 states specific verbs (load, go back/forward/reload) and resources (URL, tab history), and explicitly distinguishes from siblings like tab_new and click. An agent can understand exactly what this tool does 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?

It specifies when to use this tool vs alternatives: 'Use tab_new to open a page in a new tab and click on links to follow them.' It also clarifies 'Give either url or action', removing ambiguity about argument combinations.

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