Skip to main content
Glama

browser_traverse_menu

Auto-traverse page navigation menus by clicking each item and checking console, page, and network errors per step. Validates navigation functionality for regression testing.

Instructions

Auto-traverse page navigation menus level by level (1/2/3 tier), clicking each item while checking console errors, page errors, and network errors per step. Auto-detects standard nav containers, sidebars, and UI framework menus (Ant Design/Element UI); falls back to full-page link scan if not found.

中文详情:

  • 用途:自动遍历页面导航菜单,逐级点击一级/二级/三级菜单项,每步检查控制台/页面/网络错误,验证功能链路是否正常

  • 何时使用:站点功能回归测试时;页面健康检查时;新版本上线前菜单遍历验证时;UI 框架迁移后菜单稳定性测试时

  • 输出:{ ok: boolean, totalItems: number, clickedItems: number, results: array, errors: array } — 每项含 { text, url, urlChanged, pageTitle, consoleErrors, networkErrors, success }

  • 参数:

    • maxDepth (number, 可选):最大遍历深度(1=仅一级,2=含二级,3=含三级),默认 3

    • maxItems (number, 可选):最大点击次数,防止无限遍历,默认 30

    • waitMs (number, 可选):每次点击后的等待时间(毫秒),默认 500

    • includeSubMenus (boolean, 可选):是否自动展开并点击子菜单,默认 true

  • 错误:未找到菜单容器时降级扫描全页面链接;遍历超时会在 results 中标记 timeout

  • 示例:{"maxDepth":2,"maxItems":20,"waitMs":800,"includeSubMenus":true}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitMsNo每次点击后的等待时间(毫秒),默认500
maxDepthNo最大遍历深度(1=仅一级,2=含二级,3=含三级),默认3
maxItemsNo最大点击次数,防止无限遍历,默认30
includeSubMenusNo是否自动展开并点击子菜单,默认true
Behavior5/5

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

No annotations are provided, so the description carries full burden. It details auto-detection of nav containers, fallback to full-page link scan, error checking per step, output structure, and timeout handling.

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 well-structured with English summary, Chinese details, and bullet points. While bilingual, it is efficient and covers all key aspects without redundancy.

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

Completeness5/5

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

For a complex tool with no output schema, the description includes output structure, error handling, parameter details, and fallback behavior. It is complete and actionable.

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

Parameters4/5

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

Schema coverage is 100% with descriptions. The description adds context beyond schema by explaining default values, behavior (e.g., includeSubMenus default true), and example usage.

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 tool's purpose: auto-traverse page navigation menus, clicking each item while checking errors. It distinguishes from siblings like browser_click (single click) and browser_navigate (navigation).

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

Usage Guidelines5/5

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

The description provides explicit usage scenarios in Chinese (e.g., regression testing, health check, menu traversal verification, stability testing). It also describes fallback behavior and 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