Skip to main content
Glama

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
NameRequiredDescriptionDefault
deviceYesThe device identifier to use. Use mobile_list_available_devices to find which devices are available to you.

Implementation Reference

  • 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(", ")}`;
    	}
    );
Behavior3/5

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

The annotations already declare readOnlyHint=true, indicating this is a safe read operation. The description adds context by specifying it lists 'installed apps,' which clarifies the scope beyond just apps, but it doesn't disclose additional behavioral traits like rate limits, pagination, or error conditions. No contradiction with annotations exists.

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 a single, efficient sentence that directly states the tool's purpose without any unnecessary words, making it highly concise and front-loaded for quick understanding.

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?

Given the tool's low complexity (one parameter, read-only annotation), no output schema, and simple purpose, the description is complete enough for an agent to use it correctly. It could be slightly improved by mentioning the output format, but the lack of an output schema doesn't severely hinder usability in this context.

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?

The input schema has 100% description coverage, with the 'device' parameter well-documented in the schema itself. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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 specific verb ('List') and resource ('all the installed apps on the device'), and it distinguishes this tool from siblings like mobile_install_app, mobile_launch_app, and mobile_uninstall_app by focusing on listing rather than modifying apps.

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 implies usage for retrieving installed apps, and the input schema's description for the 'device' parameter references mobile_list_available_devices as an alternative for finding devices, providing clear context. However, it doesn't explicitly state when not to use this tool or compare it to all relevant siblings like mobile_list_elements_on_screen.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EmpathySlainLovers/MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server