agent-browser-mcp

Overview Schema Source Related Servers Discussions Admin

browser_is_visible

Check whether a specified element is visible on the page using its selector or reference. Returns visibility status to guide subsequent browser automation actions.

Instructions

Check if an element is visible

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": "browser_is_visible"
  }
}

Input Schema

Name	Required	Description	Default
`selector`	Yes	Selector or ref for the element
`sessionId`	No	Browser session ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Aug 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only check but does not specify the return type, waiting behavior, or definition of 'visible' (e.g., CSS visibility vs. layout presence).

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 a single concise sentence, front-loaded with the action and resource. Every word earns its place, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should explain the return value (e.g., boolean true/false), but it only states the action. It also lacks usage context or alternative guidance, making it incomplete for an agent despite the tool's simple interface.

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

Parameters3/5

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

Schema description coverage is 100% with both parameters adequately described ('Selector or ref for the element' and 'Browser session ID'). The description adds no additional parameter meaning beyond what the schema already provides, so the baseline of 3 applies.

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 uses a specific verb 'Check' and clearly identifies the resource 'element visibility'. It distinguishes from sibling tools like browser_is_enabled and browser_is_checked by focusing on visibility rather than other states.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as browser_is_enabled or browser_is_checked. There is no context about element visibility checking or exclusions, leaving the agent without usage direction.

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