Skip to main content
Glama
Sign In
mcp-browser-automation

mcp-browser-automation

by ritesh-jain
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

navigate

Opens a specified URL in an automated browser. Supports optional mobile emulation and custom viewport sizes.

Instructions

Navigate to a URL in the browser

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": "navigate"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to navigate to
isMobileNo
viewportNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations available, the description alone must disclose behavioral traits. It only states the basic action without revealing whether it waits for page load, how it handles invalid URLs, or if it interacts with the existing viewport state. This leaves significant unknowns for the agent.

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 a single, front-loaded sentence with no wasted words. However, it is so brief that it omits crucial details, making it slightly less useful than a concise but well-specified description.

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?

For a tool with three parameters, one nested object, no output schema, and no annotations, the description is incomplete. It does not explain return behavior, optional parameter usage, or any caveats, which is insufficient for confident tool invocation.

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

Parameters1/5

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

Schema description coverage is only 33% (only 'url' is described), and the description adds no meaning for 'isMobile' or 'viewport'. It fails to compensate for the low coverage, leaving the agent without understanding how these optional parameters affect navigation.

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 action ('Navigate') and the target ('a URL'), with a specific verb+resource. It naturally distinguishes itself from sibling tools like capture_screenshot or execute_js, which serve different purposes.

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 navigate versus alternatives like execute_js or interact. There is no mention of preconditions, such as needing a page to be already loaded, or when it is appropriate to navigate directly.

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