Skip to main content
Glama

browser_find_page

Locate target pages like login, dashboard, or settings by checking URL, title, CSS selectors, and SPA buttons. Returns matched links and optionally auto-navigates.

Instructions

Smart page discovery: locate target page (login/signup/home/dashboard/admin/settings/profile/etc.) by priority chain (URL path > title > CSS selector > SPA button text > nav region > visible text), returns matched links and suggested navigation URL; optionally auto-navigate.

中文详情:

  • 用途:根据目标页面关键词(login/signup/home/dashboard/admin/settings/profile 等)快速定位页面,支持 SPA 应用的按钮导航发现

  • 何时使用:测试入口页(登录/注册/后台)未直接知晓 URL 时;SPA 应用通过按钮导航时;导航回归测试时;权限切换后定位目标页时

  • 输出:{ ok: boolean, target: string, matched: boolean, matchMethod: string, score: number, links: array, buttons: array, suggestedUrl: string, navigated: boolean }

  • 参数:

    • target (string, 必填):目标页面类型,可选 login/signup/home/dashboard/admin/settings/profile/search/cart/checkout/forgot-password/reset-password/logout/all

    • navigate (boolean, 可选):是否自动导航到发现的页面,默认 false

    • baseUrl (string, 可选):基础 URL,用于尝试常见路径,不指定时从当前 URL 推导

  • 错误:target 值非法抛出 'Invalid target';未匹配且 navigate=true 时返回 matched=false

  • 示例:{"target":"login","navigate":true,"baseUrl":"https://example.com"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYes目标页面类型:login / signup / home / dashboard / admin / settings / profile / search / cart / checkout / forgot-password / reset-password / logout / all
baseUrlNo基础URL,用于尝试常见路径。不指定时从当前页面URL推导
navigateNo是否导航到发现的页面(如果还没在目标页面),默认false
Behavior5/5

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

No annotations provided, so description carries full burden. Details priority chain order, output fields (matched, matchMethod, score, etc.), error conditions ('Invalid target' for invalid target value), and behavior when navigate=true fails. Fully transparent.

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?

Front-loaded English summary followed by structured Chinese details. Slightly verbose due to repetition, but justified given the complexity. Every section serves a purpose.

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 3-parameter tool with no output schema, description provides output structure, error handling, use cases, and an example. Complete for agent to decide and invoke correctly.

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%, so baseline is 3. Description adds value beyond schema: explains target enum values, default for navigate (false), derivation of baseUrl from current URL when omitted, 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: 'Smart page discovery: locate target page...' with specific verb (locate) and resource (target page). It distinguishes from siblings by specifying the priority chain and supported target types.

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?

Provides explicit when-to-use scenarios in Chinese (e.g., when URL unknown, SPA navigation, regression tests). Lacks explicit alternatives among siblings but covers context well.

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