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

Lists all on-screen elements with refs, coordinates, and labels, enabling precise interaction via clicks. Re-list only after layout changes.

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.6
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. 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"
+}
  3. 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"
+]
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark this as read-only and open-world, but the description adds important behavioral context: refs and coordinates are valid only while the screen does not change. It also clarifies the returned fields, though it does not discuss filtering, result size, or ordering.

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 three tight sentences, front-loaded with the core action and followed by integration and freshness caveats. Every sentence earns its place without redundancy.

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?

With no output schema, the description usefully summarizes return contents and ref validity. The input schema covers parameters, and annotations cover safety, leaving no significant gap for an agent to invoke the tool correctly.

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%, so the device and format parameters are already fully documented in the input schema. The description adds no additional meaning about parameter syntax, defaults, or effects, making 3 the appropriate baseline.

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 states a specific verb and resource: 'List elements on screen,' and enumerates what is returned (ref, coordinates, display text or accessibility label). This clearly distinguishes the tool from siblings like mobile_get_screen_size or mobile_take_screenshot.

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?

It explains how to use the output with mobile_click_on_screen_at_coordinates and gives a clear condition for re-listing after navigation or layout change. It lacks explicit guidance on when to prefer this over alternatives such as screenshots or other screen-inspection tools.

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