Skip to main content
Glama

web_navigate

Directs a browser tab to a specified URL, optionally targeting a tab ID, so AI agents can move between pages during automation.

Instructions

Navigate a tab to a URL.

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": {
      "url": "<url>"
    },
    "name": "web_navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
target_idNoTab id from web_tabs. Omit to use the first/active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It says what action occurs but not what the tool returns, whether navigation waits for load, how errors are surfaced, or what happens to the current page state.

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 definition is a single front-loaded sentence with no filler. It is concise, though its brevity contributes to the gaps in guidance and behavior rather than being a structural flaw.

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

Completeness2/5

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

With no annotations, no output schema, and only 50% schema description coverage, the one-sentence description is not complete enough. It omits the distinction from web_new_tab/web_switch_tab and does not explain navigation behavior or return semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: target_id is documented in the schema, while url has no description. The description adds no parameter-level meaning beyond restating that a URL is involved, so it does not compensate for the undocumented url parameter.

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?

The description states a specific verb ('Navigate') and resource ('a tab to a URL'), so the core action is clear. It does not distinguish this from siblings such as web_new_tab or web_switch_tab, leaving the agent to infer that this targets an existing tab.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no when-not-to-use condition, and no named alternative. The only implied usage is navigating an existing tab, but the agent must infer that from the phrase 'a tab' rather than from stated guidance.

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