lyra-browser

Official

Overview Schema Source Related Servers Discussions Admin

highlight_element

Draws a visible outline around a page element in the shared browser window so the user can see exactly which element an agent is referencing during a collaborative session.

Instructions

Outline an element in the shared window so the user can see what you mean.

Requires an attended (headful) session — in headless mode there is no one to show it to, so this returns unattended.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "selector": "<selector>"
    },
    "name": "highlight_element"
  }
}

Input Schema

Name	Required	Description	Default
`selector`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the headful-session prerequisite and the exact failure behavior (returns "unattended" in headless mode), which an agent needs before calling. It omits edge cases such as what happens with an invalid or unmatched selector, but output_schema exists so return values need not be restated.

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 short sentences, front-loaded with the purpose then the operative constraint. No filler; every clause earns its place.

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?

For a one-parameter visual tool with an output schema already documenting returns, the description covers purpose and the key session constraint adequately. The only real gap is selector semantics, which is left to the schema that does not describe it.

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

Parameters2/5

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

Schema description coverage is 0% and the single required parameter "selector" has no schema description, so the description must compensate. It only implies that a selector identifies "an element" without stating the accepted format (CSS, XPath) or matching behavior, leaving the parameter under-specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Outline an element") plus the reason ("so the user can see what you mean"), which makes the visual-emphasis intent distinct from action siblings like click or hover. It does not explicitly name an alternative tool, so it stops short of full sibling differentiation.

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?

Gives a clear usage condition: it requires an attended (headful) session, and in headless mode it is inapplicable. This is an explicit when-not-to-use constraint, though it names no alternative sibling for the headless case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.