Skip to main content
Glama

navigate

Loads a URL in a specified browser tab, or sends that tab back, forward, or reload, then waits for the page to finish loading.

Instructions

Navigate a tab to a URL, or go "back", "forward" or "reload". Waits for the page to finish loading.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA URL, or one of: back, forward, reload
tabIdYesTab ID, from tabs_list or tab_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.8

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute one genuinely useful behavioral fact: it blocks until the page finishes loading. It says nothing about failure modes, timeout behavior, or what happens with an invalid URL, which matter for a network-dependent operation.

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?

Two short sentences, capability first and the blocking-load trait second. Nothing is padded and no clause is wasted.

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?

For a two-parameter navigation tool with full schema coverage and no output schema, the definition covers what the tool does and when it returns. The remaining gap is error/timeout behavior, which is minor given the tool's simplicity.

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 both parameters are already documented, including the back/forward/reload sentinel values. The description restates the sentinel list without adding format, encoding, or constraint detail, so baseline 3 is appropriate.

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?

"Navigate a tab to a URL" names a specific verb and resource, and the back/forward/reload enumeration pins down the exact scope. It is clearly distinguishable from click, tab_create or javascript, though it does not explicitly name a sibling to contrast with.

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?

The description states the capability but gives no when-to-use conditions, no exclusions (e.g. when to prefer click on a link or tab_create for a new tab), and no prerequisites such as needing an existing tabId. The agent must infer all of this.

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