Skip to main content
Glama

Click an element

click_element
Destructive

Click on a page element

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": {
      "sessionId": "<sessionId>",
      "selector": "<selector>"
    },
    "name": "click_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
selectorYesCSS selector of the element to click
sessionIdYesSession ID of the connected browser

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sessionId / description
      Previous value: -"ID de sesión del navegador conectado"New value: +"Session ID of the connected browser"
  2. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the safety profile is known from structured data. The description adds nothing beyond that: it does not say that a click can trigger navigation, form submission, or other irreversible side effects, nor whether the call waits for the resulting page state. For a destructive open-world action, that is a real gap.

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

Conciseness3/5

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

It is a single short sentence with no wasted words and the action is front-loaded. But the brevity comes at the cost of under-specification rather than being tightly informative.

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 what a click returns or how failures surface, and it does not. For a destructive, open-world interaction tool, the agent is left without guidance on side effects, waiting behavior, or error conditions.

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 selector and sessionId documented in the schema itself. The description adds no extra meaning about selector syntax, element visibility requirements, or failure behavior, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Click on a page element" states a concrete verb and resource, so an agent knows the basic action. However, it is the bare minimum: there is no scope, no mention of the CSS-selector targeting model, and nothing that separates it from siblings such as type_text or get_elements beyond the verb itself.

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?

The description gives no when-to-use guidance, no precondition that a browser session must already be connected, and no pointer to alternative tools for reading or interacting with elements. The agent must infer all of this from the schema and sibling names.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources