Skip to main content
Glama
Sign In
agent-browser

agent-browser

by EgiStr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

click

Activates a webpage element using a page snapshot reference or a Playwright selector such as CSS, text, or role.

Instructions

Click an element by page_snapshot ref or Playwright selector (css=, text=, role=...).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "click"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNo
selectorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden, and it only hints that refs originate from page_snapshot. It says nothing about auto-waiting, scroll-into-view, whether the click can trigger navigation, error behavior when the element is missing, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single dense sentence with the verb and both addressing modes front-loaded and zero filler. It is arguably under-sized for a mutation tool, but nothing present is wasted.

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?

An output schema exists so return values needn't be described, but for a write action with no annotations and two nullable parameters, the description should still cover selector precedence and failure/wait semantics. Those omissions leave the definition short of what an agent needs to call it reliably.

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 coverage is 0% and the schema gives only bare "Ref"/"Selector" titles, so the description must compensate. It does add genuine value — ref provenance from page_snapshot and selector syntax examples (css=, text=, role=) — but omits mutual exclusivity and which one wins when both are present.

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 ("Click") and resource ("an element") plus the two accepted addressing schemes ("page_snapshot ref or Playwright selector"). That clearly separates it from sibling navigation/input tools like type_text and press_key, though it never names a sibling explicitly.

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 on when to use ref versus selector, whether both may be supplied, or the precedence between them — a real gap since both parameters are optional with default null. There is also no stated prerequisite that a ref must come from a prior page_snapshot call, leaving the agent to infer it.

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

Deploy Server

Other Tools