Skip to main content
Glama
munimtechnologies

Computer Use

by munimtechnologies
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Navigate browser tab

browser_navigate
Destructive

Navigates a specified browser tab to a new URL, replacing the current page. Use to load a different site; open another tab to preserve current page and snapshot afterward.

Instructions

Point one of the agent's tabs at a different URL, replacing the current page; unsaved page state is lost. Use browser_open_tab to keep the current page and open another. Follow with browser_snapshot, since element indices reset after navigation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute URL to load in the tab
tab_idYestab_id of one of the agent's tabs, from browser_open_tab or browser_list_tabs
session_idNoStable task or thread ID. Pass the same value on every browser call for this task. Different IDs isolate tabs and cleanup within one MCP process. Omit for the default process session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.3
    • addedInput schema / properties / session_id
      Added value: +{
+  "description": "Stable task or thread ID. Pass the same value on every browser call for this task. Different IDs isolate tabs and cleanup within one MCP process. Omit for the default process session.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.3.1
    • addedInput schema / properties / tab_id / description
      Added value: +"tab_id of one of the agent's tabs, from browser_open_tab or browser_list_tabs"
    • addedInput schema / properties / url / description
      Added value: +"Absolute URL to load in the tab"
  3. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already include destructiveHint=true and readOnlyHint=false, but the description adds valuable specifics: 'unsaved page state is lost' and 'element indices reset after navigation.' These details go beyond what annotations convey, explaining the exact consequences of the action. No contradiction with 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?

The description is two sentences with zero wasted words. The main action is front-loaded, the alternative is given next, and the follow-up is last. Every sentence serves a purpose: action, alternative, and post-requisite.

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 destructive behavior and no output schema, the description covers all essential aspects: what it does, when to use an alternative, and what to do after. It also implicitly explains why the snapshot is needed (element indices reset). An agent can call this tool correctly with the information provided.

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 all three parameters (url, tab_id, session_id) are documented in the schema. The description does not add extra parameter semantics beyond what the schema provides, but it doesn't need to; the schema is sufficient. Baseline of 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 clearly states the tool's function: 'Point one of the agent's tabs at a different URL, replacing the current page.' It uses a specific verb (navigate), names the resource (tab), and distinguishes itself from sibling browser_open_tab by noting the replacement behavior. The mention of losing unsaved page state further clarifies the destructive nature.

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?

The description explicitly tells the agent when not to use this tool: 'Use browser_open_tab to keep the current page and open another.' It also provides a clear follow-up action: 'Follow with browser_snapshot, since element indices reset after navigation.' This gives the agent concrete sequencing and alternative selection criteria.

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