Skip to main content
Glama

web_click

Clicks a page element by CSS selector or matching visible text, enabling AI agents to trigger buttons, links, and controls in Chrome.

Instructions

Click an element by CSS 'selector', or the first clickable element whose visible text contains 'text'.

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

Input Schema

NameRequiredDescriptionDefault
textNo
selectorNo
target_idNoTab id from web_tabs. Omit to use the first/active tab.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful matching behavior: text is a case-insensitive-style 'contains' match against visible text and resolves to the FIRST clickable match, which tells the agent ambiguity is resolved arbitrarily. It omits failure behavior (no match, hidden element), whether it waits or scrolls into view, and side effects such as navigation triggering.

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?

A single sentence that front-loads the verb and the two targeting modes with 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.

Completeness3/5

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

For a no-annotation, no-output-schema action tool this covers targeting adequately, but an agent cannot tell what a failed click returns, whether it blocks until the element exists, or whether the click may change page state. Those gaps matter for an action tool with side effects.

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 33%, and the description supplies semantics for both 'selector' and 'text' including the 'visible text contains' matching rule, while 'target_id' is documented in the schema itself. However, it does not resolve precedence or interaction between 'selector' and 'text' when both are provided, leaving the key ambiguity unresolved.

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 both targeting modes: a CSS 'selector' or the first clickable element whose visible text contains 'text'. That is concrete enough to distinguish it from unrelated siblings like web_type and web_navigate, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

The description implies usage through the two matching strategies, but never says when to prefer selector over text, what happens when both are supplied, or that text entry should go through web_type instead. Guidance is implied rather than stated.

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