Skip to main content
Glama
raultov

chrome-debug-mcp

by raultov
OverviewSchemaRelated ServersScoreDiscussions(1)
Rust
Local

click_element

Click a visible DOM element by CSS selector to trigger click handlers, form submissions, or navigation in Chrome.

Instructions

Triggers a native mouse click event on a DOM element identified by CSS selector, executing click handlers and form submissions. Side effects: may trigger page navigation, form submission, or modify DOM state. Prerequisites: element must exist and be visible (getBoundingClientRect must return valid coordinates). Returns: success confirmation with click coordinates. Use this to interact with buttons, links, checkboxes. Alternatives: 'fill_input' for text input, 'evaluate_js' for complex interactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tab_idNoThe Tab ID of the target tab. Omit to use the active tab.
selectorYesCSS selector identifying the target element. Constraints: valid CSS selector string matching a single DOM element. Interactions: must resolve to exactly one visible element or operation fails. Defaults to: None (required).
instance_idNoChrome instance id from open_instance/list_instances. Omit for the default instance.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changedv1.3.2
    • removedInput schema / properties / instance_id / nullable
      Removed value: -true
    • removedInput schema / properties / tab_id / nullable
      Removed value: -true
  2. Changed2 schema fields changedv1.0.11
    • addedInput schema / properties / instance_id
      Added value: +{
+  "description": "Chrome instance id from open_instance/list_instances. Omit for the default instance.",
+  "nullable": true,
+  "type": "string"
+}
    • addedInput schema / properties / tab_id
      Added value: +{
+  "description": "The Tab ID of the target tab. Omit to use the active tab.",
+  "nullable": true,
+  "type": "string"
+}
  3. Changed1 schema field changedv1.0.7
    • changedInput schema / properties / selector / description
      Previous value: -"CSS selector for the element to click"New value: +"CSS selector identifying the target element. Constraints: valid CSS selector string matching a single DOM element. Interactions: must resolve to exactly one visible element or operation fails. Defaults to: None (required)."
  4. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of disclosure. It clearly lists side effects (page navigation, form submission, DOM state change), prerequisites (visibility), and the return value (click coordinates). This is comprehensive and does not contradict any structured data.

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 three purposeful sentences, front-loaded with the main action and side effects, with no filler or repetition. Every sentence contributes value.

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

Completeness5/5

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

The description covers purpose, side effects, prerequisites, alternatives, and return value. With no output schema, it explains what to expect (click coordinates). For a click tool, this is complete; nothing an agent needs to call it correctly is missing.

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%, so the baseline is 3. The description does not add new meaning to the parameters themselves; the only extra context, the selector mutability constraint, is already present in the schema.

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 states a specific action ('triggers a native mouse click'), identifies the resource ('DOM element identified by CSS selector'), and notes the effects ('click handlers and form submissions'). It also distinguishes from siblings by naming alternatives like fill_input and evaluate_js.

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

Usage Guidelines5/5

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

It explicitly lists the intended use cases (buttons, links, checkboxes) and names the alternative tools for text input and complex interactions, giving clear routing. It also mentions the prerequisite that the element must exist and be visible.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/raultov/chrome-debug-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server