Skip to main content
Glama

browser_navigate

Navigate forward, back, refresh, or reload the browser page with configurable wait conditions.

Instructions

Navigate the browser: go forward, back, refresh, or reload the current page with configurable wait conditions.

中文详情:

  • 用途:控制浏览器导航操作(前进/后退/刷新/重新加载当前页面)

  • 何时使用:在 browser_open 打开页面后需要控制加载状态时;表单提交后需要 reload 重置状态时;测试浏览器后退/前进按钮行为时;页面资源加载不完整需要 refresh 时

  • 输出:{ ok: boolean, url: string, action: string, timestamp: string }

  • 参数:

    • action (string, 必填):导航操作,可选 forward / back / refresh / reload,默认 refresh

    • waitUntil (string, 可选):等待条件,可选 domcontentloaded / load / networkidle,默认 domcontentloaded

    • timeout (number, 可选):超时毫秒数,默认 30000

  • 错误:超时抛出 'Timeout XXXXms exceeded';无效 action 值抛出 'Invalid action'

  • 示例:{"action":"refresh","waitUntil":"networkidle","timeout":10000}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes导航操作:forward(前进)、back(后退)、refresh(刷新)、reload(重新加载)refresh
timeoutNo超时时间,单位毫秒,默认30000
waitUntilNo等待条件:domcontentloaded(DOM加载完成)、load(页面完全加载)、networkidle(网络空闲)domcontentloaded
Behavior3/5

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

With no annotations, the description carries the burden. It mentions navigation behavior, wait conditions, timeout, and error types, but does not clearly state if the tool is read-only or whether it modifies state. The behavioral coverage is adequate but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The English sentence is front-loaded and clear, but the lengthy Chinese section duplicates schema info and adds redundancy. A more streamlined description would be better.

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?

Despite no output schema, the description defines the output structure and lists error cases. It covers parameters, usage contexts, and default values, making it fairly complete for a navigation tool.

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 baseline is 3. The description adds an example and repeats parameter explanations from the schema, providing marginal extra value. No significant new semantics beyond the schema.

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 clearly states 'Navigate the browser' and lists specific actions (forward, back, refresh, reload), making the tool's purpose unambiguous. It does not explicitly contrast with sibling tools, but the distinct set of actions differentiates it adequately.

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

Usage Guidelines4/5

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

The description includes a '何时使用' section that specifies when to use the tool: after browser_open, after form submit, for testing navigation, etc. This provides explicit usage context, though it does not discuss when not to use it or name direct alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/validpilot/ai-verify-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server