Skip to main content
Glama

browser_highlight

Add a colored border and shadow to any page element for visual debugging and human observation. Use it to highlight elements during inspections or reviews.

Instructions

Highlight a specific element on the page with a colored border and shadow for human observation and debugging. Effect persists until page refresh.

中文详情:

  • 用途:在页面上高亮显示指定元素(默认红色边框和阴影),便于人工观察和调试

  • 何时使用:调试元素定位问题时;演示/评审时强调某个元素;视觉走查时标记可疑元素;自动化失败后人工复核时

  • 输出:{ ok: boolean, selector: string, color: string, timestamp: string }

  • 参数:

    • selector (string, 必填):要高亮的元素选择器

    • color (string, 可选):高亮颜色,支持 CSS 颜色值,默认 red

  • 错误:selector 无匹配抛出 'element not found';color 值非法会使用默认红色

  • 示例:{"selector":".error-message","color":"#ff6600"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo高亮颜色,支持CSS颜色值,默认为红色(red)
selectorYes要高亮的元素选择器
Behavior5/5

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

With no annotations provided, the description fully discloses behavior: effect persists until page refresh, error handling for unmatched selector ('element not found') and invalid color (defaults to red), and the output format. This is comprehensive for a simple tool.

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?

The description is well-structured with an English summary followed by a detailed Chinese section using bullet points for usage, output, parameters, errors, and example. Every sentence serves a purpose, and no information is redundant.

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?

The description covers purpose, usage guidelines, parameter details, error scenarios, and behavioral traits. Given the simple nature of the tool and no output schema, it provides everything needed for correct invocation.

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?

Although schema coverage is 100%, the description adds value by explaining that color supports CSS color values and defaults to red, and provides an example JSON. This goes beyond the schema's minimal descriptions.

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 that the tool highlights a specific element with a colored border and shadow for human observation and debugging, with the effect persisting until page refresh. This specific verb+resource combination distinguishes it from siblings like browser_find_element or browser_screenshot_element.

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 Chinese description explicitly lists when to use: debugging element positioning, demo/review emphasis, visual walkthrough marking suspicious elements, and manual review after automation failure. While it doesn't list when not to use, the guidance is clear and provides practical contexts.

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