Skip to main content
Glama
zumerlab

SnapSurf

Official
by zumerlab
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Local

Click, type, select or press Enter

browser_act
Destructive

Act on web pages by clicking elements, typing text, selecting options, or pressing Enter. Confirms each resolved element and supports verification with subsequent checks.

Instructions

Act on the page: click (by id from the digest/find, or "x,y"), type (into the focused element — click it first), select a native single-select option by target id and exactly one of value or label (exact, unique match), or enter. Click and select auto-scroll and CONFIRM role/name of the resolved element: read that echo before continuing. Select refuses non-native, multiple, disabled, hidden or covered controls and disabled/ambiguous options. It dispatches input/change when the option changes, does not echo the supplied choice, omits choice arguments from audit logs, and preserves the observation baseline. Privacy rules and readonly policy apply. After EVERY action, call browser_verify, even when select reports selectionChanged:false.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoREQUIRED for type: the text to type into the focused element
labelNoSelect only: exact visible option label. Cannot be combined with value.
valueNoSelect only: exact option value, including an empty string. Cannot be combined with label.
actionYesclick REQUIRES target; type REQUIRES text; select REQUIRES target and exactly one of value/label; enter needs neither
targetNoREQUIRED for click/select: id n_xxx from digest/find. Click also accepts "x,y".
sessionIdNooptional: the session this call belongs to (from browser_session_open). Omitted uses the shared default session.

Schema Changelog

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

  1. Changed5 schema fields changedv0.1.3
    • changedInput schema / properties / action / description
      Previous value: -"click REQUIRES target; type REQUIRES text; enter needs neither"New value: +"click REQUIRES target; type REQUIRES text; select REQUIRES target and exactly one of value/label; enter needs neither"
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "click",
-  "type",
-  "enter"
-]New value: +[
+  "click",
+  "type",
+  "select",
+  "enter"
+]
    • addedInput schema / properties / label
      Added value: +{
+  "description": "Select only: exact visible option label. Cannot be combined with value.",
+  "type": "string"
+}
    • changedInput schema / properties / target / description
      Previous value: -"REQUIRED for click: id n_xxx from the digest/find, or \"x,y\""New value: +"REQUIRED for click/select: id n_xxx from digest/find. Click also accepts \"x,y\"."
    • addedInput schema / properties / value
      Added value: +{
+  "description": "Select only: exact option value, including an empty string. Cannot be combined with label.",
+  "type": "string"
+}
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

The description discloses important behaviors: auto-scrolling, confirmation of resolved element role/name, refusal conditions for select, input/change dispatch, no echoing of supplied choices, audit log omissions, and preservation of the observation baseline. These details align with the destructiveHint and readOnlyHint annotations and go well beyond them.

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

Conciseness4/5

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

The description is dense but mostly earns its length because the tool has nuanced behaviors. A few phrases, such as 'privacy rules and readonly policy apply,' are somewhat vague, and the repeated select-specific details could be tightened, but the structure is logical and front-loaded.

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 the tool's complexity and the absence of an output schema, the description provides enough operational detail: valid action combinations, select refusal conditions, post-action verification, and observable effects like selectionChanged. The agent has sufficient context to invoke the tool correctly.

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

Parameters5/5

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

The schema covers all parameters, and the description adds meaningful semantics: click target can be an id or x,y coordinates, type requires a focused element, select requires exact unique match, and value/label are mutually exclusive. This significantly helps the agent pick and populate the right 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?

The description clearly defines the tool as a page-action tool supporting click, type, select, and enter, with specific requirements for each. It is easily distinguished from sibling tools like browser_find and browser_verify, which have different responsibilities.

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?

The description gives strong practical guidance, such as clicking before typing, requiring exactly one of value/label for select, and calling browser_verify after every action. It does not explicitly compare against alternatives, but the action-specific constraints and post-action instruction provide clear usage context.

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/zumerlab/snapsurf'

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