Skip to main content
Glama
mobile-next

Mobile Next MCP Server

Official
by mobile-next
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Screen Elements

mobile_list_elements_on_screen
Read-only

Enumerate visible UI elements on a device screen with refs, coordinates, and labels to enable targeted clicking via coordinates.

Instructions

List elements on screen with their ref, coordinates, and display text or accessibility label. Use the ref with mobile_click_on_screen_at_coordinates. Refs and coordinates stay valid as long as the screen does not change; re-list only after navigation or a layout change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.
formatNoOutput format. "text" (default) is one compact line per element, "json" is a json array

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.3
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Output format. \"text\" (default) is one compact line per element, \"json\" is a json array",
+  "enum": [
+    "text",
+    "json"
+  ],
+  "type": "string"
+}
  2. Changed4 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"
+}
    • removedInput schema / properties / noParams
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {},
-  "type": "object"
-}
    • changedInput schema / required
      Previous value: -[
-  "noParams"
-]New value: +[
+  "device"
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the read-only and dynamic nature of the tool. The description adds valuable behavioral context: that refs and coordinates remain valid only until the screen changes, and that a re-list is required after navigation or layout changes. This goes beyond the annotations and helps the agent anticipate when results become stale.

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, front-loaded with the primary purpose and then the usage caveat. There is no redundant information, and every sentence earns its place. The guidance on ref validity and re-listing is concise and directly actionable.

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?

For a simple read-only list tool, the description covers everything an agent needs: what it returns (ref, coordinates, text/label), how to use the ref (with a specific sibling tool), and when to refresh (after screen changes). With annotations covering safety and no output schema required, nothing essential 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% – both device and format parameters are fully described in the input schema. The description adds no extra parameter semantics beyond what the schema provides. Since the schema does the heavy lifting, a baseline score of 3 is appropriate.

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 states the tool lists screen elements with ref, coordinates, and display text or accessibility label. It explicitly names the sibling tool mobile_click_on_screen_at_coordinates for using the ref, which distinguishes it from other list tools in the sibling set (e.g., mobile_list_apps, mobile_list_available_devices). The verb 'list' plus resource 'screen elements' is specific and unambiguous.

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 explicit guidance on when to use the tool again: 're-list only after navigation or a layout change' and notes that refs/coordinates stay valid while the screen is unchanged. It also directs the agent to use the ref with a specific sibling tool, providing clear follow-up context. It doesn't explicitly state when not to use it, but there is no direct alternative among siblings, so this is adequate.

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