Skip to main content
Glama

browser_find

Locate UI elements by text or role, or find pages by target type (e.g., login, settings). Supports navigation to discovered pages.

Instructions

智能查找工具(v1.9.5 起合并 browser_find_element/find_page)。通过 mode 参数区分子模式:element(默认,按文本描述或 ARIA 角色智能定位页面元素)/ page(按目标页面关键词定位页面,支持 SPA 按钮导航发现)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo查找模式:element(默认,按文本/角色定位元素)/ page(按关键词定位页面)element
roleNo元素角色:button/link/input/textbox/checkbox/radio/combobox 等(mode=element 时使用)
textNo要查找的元素文本(mode=element 时必填)
limitNo返回数量,默认 5(mode=element 时使用)
targetNo目标页面类型:login/signup/home/dashboard/admin/settings/profile/search/cart/checkout/forgot-password/reset-password/logout/all(mode=page 时必填)
baseUrlNo基础 URL,用于尝试常见路径。不指定时从当前页面 URL 推导(mode=page 时使用)
tagNameNo标签名过滤,如 button/a/input/div 等(mode=element 时使用)
navigateNo是否导航到发现的页面(如果还没在目标页面),默认 false(mode=page 时使用)
onlyVisibleNo只返回可见元素,默认 true(mode=element 时使用)
Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It mentions supporting SPA button navigation discovery for page mode, but lacks details on error handling, return format, or the 'intelligent' aspect. 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.

Conciseness5/5

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

Two sentences that front-load the tool's purpose and version, then concisely explain modes. No redundant information. Efficient and well-structured.

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?

With 9 parameters and no output schema or annotations, the description covers the two modes but omits details on return values, error conditions, or limitations (e.g., visibility, limit behavior). Adequate for basic use but incomplete for complex scenarios.

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. The description adds value by explaining the two modes and noting SPA navigation support beyond the schema descriptions. It clarifies the purpose of each mode and some parameter usage context.

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 it is a combined find tool for elements and pages, with explicit mode differentiation. It distinguishes itself from sibling tools like browser_find_element and browser_find_page by noting it is a merge since v1.9.5.

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 specifies when to use each mode (element vs page) and mentions SPA button navigation discovery for page mode. However, it does not explicitly state when not to use this tool versus alternatives, though the mode explanation provides clear context.

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