Click webpage elements using snapshot refs or CSS selectors. Snapshot refs provide reliable targeting for automated browser interactions.
Click an element. Provide either ref (from snapshot) or CSS selector. Use snapshot first to discover element refs.
| Name | Required | Description | Default |
|---|---|---|---|
| ref | No | Element ref from snapshot (e.g. 'e1', 'e2') | |
| tabId | Yes | Tab ID from create_tab | |
| selector | No | CSS selector (e.g. 'button.submit', '#login') |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It only says 'Click an element' without disclosing waiting behavior, navigation triggers, or whether it returns anything. Minimal behavioral info.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no redundant words. Front-loaded with action, then details. Highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, so description should cover return values or side effects. It doesn't. Tool is simple but lacks info on what happens after click (e.g., navigation). Barely adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so baseline is 3. Description adds value by advising to use snapshot for ref discovery, supplementing the schema's parameter descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Click an element' with specific verb and resource. It distinguishes from siblings like batch_click by mentioning ref or selector. No ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises to use snapshot first to discover refs. Provides clear context but doesn't contrast with alternatives like hover or type_text.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.