Skip to main content
Glama
mozilla

firefox-devtools-mcp

by mozilla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

navigate_page

Navigate the active Firefox tab to a specified URL, with options to wait for interactive or complete page load. Use to load pages for testing, scraping, or automation.

Instructions

Navigate selected tab to URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesTarget URL
waitNoWhen to return: 'none' (navigation started), 'interactive' (DOMContentLoaded), 'complete' (load event fired, including subresources). Omit for the default: 'interactive' for http/https/data/blob/file, 'none' for other schemes. Use 'complete' when the page must be fully loaded, e.g. before stopping a performance recording.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.3
    • addedInput schema / properties / wait
      Added value: +{
+  "description": "When to return: 'none' (navigation started), 'interactive' (DOMContentLoaded), 'complete' (load event fired, including subresources). Omit for the default: 'interactive' for http/https/data/blob/file, 'none' for other schemes. Use 'complete' when the page must be fully loaded, e.g. before stopping a performance recording.",
+  "enum": [
+    "none",
+    "interactive",
+    "complete"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / url / description
      Previous value: -"URL to navigate the page to"New value: +"Target URL"
  3. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The description adds the contextual detail that it operates on the selected tab, beyond the readOnlyHint=false annotation. However, it does not disclose side effects like document replacement or history entry creation. With annotations already signaling mutation, the description adds moderate value.

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 a single, front-loaded sentence with no filler. Every word carries meaning, making it appropriately concise.

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

Completeness3/5

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

The tool is simple and parameter semantics are fully covered by the schema, but the description lacks usage guidance and any mention of side effects. It is adequate for invocation but incomplete for correct selection among related navigation tools.

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?

Input schema coverage is 100%, so both url and wait are described in the schema. The description itself adds no parameter-level meaning, so the baseline of 3 applies.

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'), resource ('selected tab'), and target ('URL'). The phrase 'selected tab' distinguishes it from sibling tools like new_page or select_page, though it does not explicitly call them out.

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?

No guidance is provided on when to use this tool versus alternatives such as navigate_history, new_page, or select_page. The description only states what the tool does, leaving the agent to infer usage context.

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