Local MCP

Web Click

web_click

Destructive

Clicks an element on the current page. target is a CSS selector or visible text (resolved fresh each call). Clicks that SUBMIT a form preview first — call again with confirm:true to execute; plain links/buttons click directly. Returns {url, title, navigated, url_as_of}: url_as_of is "settled" when the page has finished changing, and "before_click" together with navigation_pending:true when the click started a navigation that had not finished — in that case url/title are the page BEFORE the click, NOT the destination, so do not read them as 'the click did nothing' and retry (the page is already changing); read the destination with web_read or wait for it with web_wait_for. navigated:false means the click changed no page.

Input Schema

Name	Required	Description
`target`	Yes	CSS selector or visible text of the element to click.
`confirm`	No	Required (true) to perform a click that submits a form.
`session`	No	Session name (default 'default').
`remember`	No	With confirm: true, also stop asking for this kind of action from now on. Only when the person said so ("don't ask again"). The person can revoke it in LMCP or with set_always_allowed.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / remember

Added value: +{
+  "description": "With confirm: true, also stop asking for this kind of action from now on. Only when the person said so (\"don't ask again\"). The person can revoke it in LMCP or with set_always_allowed.",
+  "type": "boolean"
+}

Changed1 schema field changedOct 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

AddedJul 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: form submits require a second confirmed call, clicks can trigger navigation, and url/title may describe the pre-click page when navigation_pending is true. The warning not to retry during a pending navigation is especially valuable and consistent with destructiveHint/openWorldHint.

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?

Purpose is front-loaded, then submit-confirm behavior, then return/navigation semantics. The length is justified by the tool's complexity and the final navigation warning prevents a common misuse, with no filler.

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?

Given a destructive, open-world browser action with an output schema, the description covers the crucial operational edge case: pending navigation vs settled page. It is complete enough for correct invocation and result interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so baseline is 3. The description still adds meaning for target (CSS selector or visible text, resolved fresh each call) and confirm (required to execute form-submitting clicks), improving how the agent should use those key parameters.

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?

States a specific verb and resource: clicks an element on the current page. It also distinguishes plain link/button clicks from form-submitting clicks, so the agent understands the core operation without opening the schema.

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

Usage Guidelines4/5

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

Explains the form-submit workflow: the first call previews, and confirm:true executes. It also tells the agent to use web_read or web_wait_for when a navigation is pending, though it does not broadly compare web_click with siblings such as web_navigate.

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

All Local MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.