Mobile Next MCP

List Apps

mobile_list_apps

Read-only

Retrieve a list of installed applications on a mobile device for automation and testing purposes using the Mobile Next MCP server.

Instructions

List all the installed apps on the device

Input Schema

TableJSON Schema

Name	Required	Description	Default
`device`	Yes	The device identifier to use. Use mobile_list_available_devices to find which devices are available to you.

Implementation Reference

src/server.ts:211-222 (handler)

Handler and registration for the 'mobile_list_apps' tool. It requires a selected robot/device, calls listApps() on it, and returns a formatted list of installed apps with names and package names.

tool(
	"mobile_list_apps",
	"List all the installed apps on the device",
	{
		noParams
	},
	async ({}) => {
		requireRobot();
		const result = await robot!.listApps();
		return `Found these apps on device: ${result.map(app => `${app.appName} (${app.packageName})`).join(", ")}`;
	}
);

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.0.0Jan 3, 2026

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"
+]

First observedAug 15, 2025

TDQS

A4/5.0

Behavior3/5

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

The description is consistent with the readOnlyHint annotation and adds the scope detail 'all installed apps'. However, it does not disclose return format, whether system apps are included, or any permission requirements. With annotations already declaring read-only, the description provides minimal additional behavioral context beyond the scope.

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?

A single concise sentence of six words. No filler or redundancy, every word 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 read-only list tool, the description combined with the schema and annotation is largely sufficient. It does not mention return format or app name specifics, but given the tool's simplicity and lack of output schema, the current description is nearly complete for selection purposes.

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%: the device parameter is fully explained as the identifier to use, with a pointer to mobile_list_available_devices. The description does not add any parameter-specific detail beyond referencing 'the device', so it relies on the schema, matching the 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 uses the specific verb 'List' with a clear resource 'installed apps on the device'. This clearly distinguishes it from sibling tools like mobile_launch_app, mobile_install_app, and mobile_list_crashes, which target different actions or data types.

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?

While no explicit alternatives or exclusions are given, the phrase 'List all the installed apps' provides clear context for when to use this tool. The schema also points to mobile_list_available_devices for device selection, which is useful guidance even though it's not in the description itself.

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