Skip to main content
Glama
HyperClockUp

DrissionPageMCPServer_Modified

by HyperClockUp

find_elements

Locate web page elements using CSS selectors, XPath, or text matching to verify existence, accessibility, and retrieve detailed attributes for browser automation tasks.

Instructions

查找页面元素(智能定位工具)

        ⚠️ 精确定位工具:基于DOM分析结果进行元素查找!
        
        🎯 主要用途:
        1. 🔍 基于get_dom_tree()结果,精确定位目标元素
        2. 📋 验证元素存在性和可访问性
        3. 🎯 获取元素的详细属性信息(id、class、text等)
        4. 🛠️ 为后续操作提供准确的选择器
        
        💡 选择器类型优先级:
        1. CSS选择器:#id、.class、[attribute](推荐)
        2. XPath://div[@class='example'](复杂定位)
        3. 文本匹配:"按钮文字"(辅助手段)
        
        Args:
            selector: 元素选择器(必须基于实际DOM结构)
            selector_type: 选择器类型(css/xpath/text)
            limit: 返回元素数量限制(避免结果过多)
            include_similar: 是否包含相似元素(智能匹配)
            
        Returns:
            str: 匹配元素的详细信息列表
            
        🚀 最佳实践:
        - 先用get_dom_tree()分析页面结构
        - 基于结构信息构建精确选择器
        - 验证找到的元素是否为目标元素
        - 将结果用于click_element()或input_text()操作
            
        Returns:
            str: 查找结果
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes
selector_typeNocss
limitNo
include_similarNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing behavioral traits: it explains the tool is for '精确定位' (precise positioning) based on DOM analysis, mentions '智能匹配' (intelligent matching) with include_similar parameter, describes return format as '匹配元素的详细信息列表' (detailed information list of matched elements), and provides practical constraints like '避免结果过多' (avoid too many results) with limit parameter. It doesn't cover error cases or performance characteristics, keeping it from a perfect score.

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 description is appropriately sized but not optimally structured: it uses emoji sections and has duplicate 'Returns' sections (appearing twice with slightly different wording). While most content is valuable, the repetition and decorative formatting reduce efficiency. The information is front-loaded with purpose and usage, but the structure could be more streamlined.

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?

Given 4 parameters with no schema descriptions, no annotations, but with output schema (implied by 'Returns' statements), the description provides good completeness: it covers purpose, usage workflow, parameter semantics, and integration with sibling tools. However, it doesn't explicitly describe error conditions or what happens when no elements match, and the duplicate Returns sections create minor confusion about output format.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by providing rich semantic context for all 4 parameters: it explains selector must be '基于实际DOM结构' (based on actual DOM structure), selector_type has three specific types with usage guidance (CSS recommended, XPath for complex, text as auxiliary), limit prevents '结果过多' (too many results), and include_similar enables '智能匹配' (intelligent matching). This adds significant meaning beyond the bare schema.

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 as '查找页面元素(智能定位工具)' (find page elements - intelligent positioning tool) and elaborates with specific verbs like '精确定位目标元素' (precisely locate target elements), '验证元素存在性和可访问性' (verify element existence and accessibility), and '获取元素的详细属性信息' (get detailed element attribute information). It distinguishes from siblings like get_dom_tree (which analyzes structure) and click_element/input_text (which perform actions on found elements).

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 guidance on when to use this tool: '基于DOM分析结果进行元素查找' (based on DOM analysis results for element finding) and '先用get_dom_tree()分析页面结构' (first use get_dom_tree() to analyze page structure). It also specifies when to use alternatives by mentioning selector type priorities (CSS for recommended cases, XPath for complex cases, text matching as auxiliary). The '最佳实践' (best practices) section clearly outlines the workflow 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/HyperClockUp/DrissionPageMCPServer_Modified'

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