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

agent-browser-mcp

by zy2755
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_navigate

Navigates to a URL and returns a snapshot of interactive page elements with click/type reference IDs. Automatically adds https:// when the protocol is missing.

Instructions

导航到 URL,返回后自动附带页面交互元素快照(带 [eN] ref 编号,可直接用于 click/type)。缺协议时自动补 https://。

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

Input Schema

NameRequiredDescriptionDefault
urlYes目标 URL
newTabNo是否在新标签页打开(默认 false,当前页导航)
snapshotNo是否在结果中附快照(默认 true)
timeoutMsNo导航超时毫秒数(默认 30000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 disclose two non-obvious behaviors: automatic https:// prefixing and a snapshot attached by default. It says nothing about navigation failure, timeout behavior, whether it waits for page load, or whether it can disturb an in-progress 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?

Two compact sentences with the return-value behavior front-loaded right after the action, and the URL-normalization rule last. No filler, though the parenthetical about ref numbering is slightly dense.

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?

Because there is no output schema, explaining that a snapshot with refs is returned is genuinely valuable and it is covered here. What is missing for a navigation primitive is failure/timeout semantics and any note on load-state guarantees, which an agent needs before chaining click/type calls.

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 coverage is 100%, so the schema already documents all four parameters and their defaults. The description adds meaning only for two of them (snapshot default, URL normalization) and says nothing about newTab or timeoutMs beyond what the schema states, so it sits at the baseline.

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?

Names a specific verb and resource (navigate to a URL) and states what comes back (an interactive-element snapshot with [eN] refs). It ties itself to browser_click/browser_type workflows, though it does not explicitly contrast itself with browser_snapshot, which also produces snapshots.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the mention that refs are 'directly usable for click/type' tells the agent this is the entry point for a click/type sequence. There is no explicit when-to-use or when-not guidance, and no mention of when to prefer browser_snapshot instead of relying on the attached snapshot.

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