Skip to main content
Glama
Mobile Next MCP Server

Mobile Next MCP Server

Official
by mobile-next

List Screen Elements

mobile_list_elements_on_screen
Read-only

Lists on-screen elements with refs, coordinates, and display text or accessibility labels so you can target taps, long presses, and drags; re-list after navigation or 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, mobile_double_tap_on_screen, mobile_long_press_on_screen_at_coordinates or mobile_drag_on_screen. Refs and coordinates stay valid as long as the screen does not change; re-list only after navigation or a layout change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "device": "<device>"
    },
    "name": "mobile_list_elements_on_screen"
  }
}

Input 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, "raw" is the unfiltered platform-specific hierarchy as JSON (mobilecli only). Raw nodes may be offscreen and do not have element refstext

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.16
    • addedInput schema / properties / format / default
      Added value: +"text"
    • changedInput schema / properties / format / description
      Previous value: -"Output format. \"text\" (default) is one compact line per element, \"json\" is a json array"New value: +"Output format. \"text\" (default) is one compact line per element, \"json\" is a json array, \"raw\" is the unfiltered platform-specific hierarchy as JSON (mobilecli only). Raw nodes may be offscreen and do not have element refs"
    • changedInput schema / properties / format / enum
      Previous value: -[
      -  "text",
      -  "json"
      -]New value: +[
      +  "text",
      +  "json",
      +  "raw"
      +]
  2. 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"
  3. 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"
      +}
  4. 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"
      +]
  5. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description's real contribution is the staleness contract for refs and coordinates. It does not discuss cost, latency, or what happens if a stale ref is used (failure mode), and defers the raw-format caveat to the schema.

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?

Three sentences, front-loaded with what comes back, then how to use it, then the caching constraint. No filler or restatement of the tool name.

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?

With no output schema, the description correctly names the returned fields and the validity window of refs, which is the critical piece an agent needs. Minor gap: no guidance on output size/truncation on element-dense screens or on failure when the device is unavailable.

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%, including a documented 'format' enum and the device lookup hint, so the schema carries parameter meaning already. The description adds nothing parameter-specific beyond the returned-field list, which matches the baseline of 3.

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?

Specific verb and resource ('List elements on screen') plus the exact payload ('ref, coordinates, and display text or accessibility label'). It is clearly distinguishable from siblings like mobile_take_screenshot or mobile_list_apps, which return different artifacts.

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?

Gives explicit downstream usage (name the four tools that consume a ref) and a re-invocation rule ('re-list only after navigation or a layout change'). It stops short of stating when NOT to use this tool, e.g. in favor of a screenshot, so no explicit alternative routing beyond the consumer list.

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