Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Click Screen

mobile_click_on_screen_at_coordinates

Clicks on a mobile screen at exact x,y coordinates or by element ref from the latest element list to trigger UI actions.

Instructions

Click on the screen, either at x,y coordinates or on an element by its ref (e.g. "@e5") from the latest mobile_list_elements_on_screen result. Prefer ref when the element is listed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNoThe x coordinate to click on the screen, in pixels. Required unless ref is given
yNoThe y coordinate to click on the screen, in pixels. Required unless ref is given
refNoElement ref from mobile_list_elements_on_screen, e.g. "@e5". Takes precedence over x,y
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.0.3
    • addedInput schema / properties / ref
      Added value: +{
+  "description": "Element ref from mobile_list_elements_on_screen, e.g. \"@e5\". Takes precedence over x,y",
+  "type": "string"
+}
    • changedInput schema / properties / x / description
      Previous value: -"The x coordinate to click on the screen, in pixels"New value: +"The x coordinate to click on the screen, in pixels. Required unless ref is given"
    • addedInput schema / properties / x / minimum
      Added value: +0
    • changedInput schema / properties / y / description
      Previous value: -"The y coordinate to click on the screen, in pixels"New value: +"The y coordinate to click on the screen, in pixels. Required unless ref is given"
    • addedInput schema / properties / y / minimum
      Added value: +0
    • changedInput schema / required
      Previous value: -[
-  "device",
-  "x",
-  "y"
-]New value: +[
+  "device"
+]
  2. Changed3 schema fields changedv1.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / device
      Added value: +{
+  "description": "The device identifier to use. Use mobile_list_available_devices to find which devices are available to you.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "x",
-  "y"
-]New value: +[
+  "device",
+  "x",
+  "y"
+]
  3. First observed

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds little about actual behavior—it does not mention side effects (e.g., triggering UI events), failure modes (e.g., off-screen coordinates), or any prerequisites beyond the device parameter. It focuses on input selection rather than behavioral outcomes.

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 two sentences with zero fluff. It front-loads the core action ('Click on the screen') and then specifies the two input modes and the preference rule. Every sentence earns its place.

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

Completeness4/5

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

For a simple click tool with no output schema, the description covers the essential information needed to invoke it correctly: the action, the two input methods, and the ref source. It could mention that it is a single tap (versus double/long press) or potential side effects, but those are largely implied by the name and annotations. The coverage is adequate for the tool's complexity.

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 100%, so each parameter is documented. The description adds meaningful context beyond the schema by explaining the ref format, its source (latest list_elements result), and the precedence of ref over coordinates, which helps an agent construct correct calls. This exceeds the baseline for fully covered schemas.

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?

The description clearly states the tool performs a click on the screen, with two input modes (coordinates or ref). It is specific about the action and resource, and the name plus description make it distinguishable from sibling tools like double-tap or long-press, though it does not explicitly name those alternatives.

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 provides a clear internal guideline—'Prefer ref when the element is listed'—which helps choose between ref and coordinates. However, it gives no explicit guidance on when to use this tool instead of siblings like double_tap or long_press, leaving that to inference from names and context.

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

Deploy Server

Other Tools